Governance — MCP Tools | Routebase Documentation

Spec validation, score weights, custom rules and severities. This page documents the Governance group of the Routebase MCP server, with the scope and the parameters of each tool.

A session that stages its tools advertises this group once the agent calls enable_toolset with the slug governance. Full-access keys, scoped keys and OAuth sessions see every tool they are allowed to call without that step.

get_breaking_changes

Identify and classify breaking changes between two specification versions. Returns changes classified as Breaking, NonBreaking, or Deprecated with migration hints. Use this for classified breaking changes; for the full structural diff use compare_versions. Requires project context.

Required scope: specs:read

Parameter	Type	Required	Description
`specId`	string	Yes	Public ID (GUID) of the API specification
`sourceVersionId`	string	Yes	Public ID (GUID) of the source (older) version
`targetVersionId`	string	Yes	Public ID (GUID) of the target (newer) version

get_header_policies

Get the headers that apply to a WHOLE endpoint, grouped by status code, after the org → project → spec cascade. Takes an endpointId; for one response use get_resolved_headers (responseId). Neither returns policy definitions — list those with list_header_policies. Requires project context.

Required scope: specs:read

Parameter	Type	Required	Description
`specId`	string	Yes	Public ID (GUID) of the API specification
`endpointId`	string	Yes	Public ID (GUID) of the endpoint

get_style_guide_rules

Get all available style guide rules with their effective severity at the organization level. Includes built-in rules and custom rules. Use list_project_style_guide_rules for how they resolve inside one project. Requires organization context.

Required scope: org:manage-governance

No parameters.

get_versioning_strategy

Get the versioning strategy configured for an API specification, including version aliases. Use this to read the strategy; to change it use set_versioning_strategy. Requires project context.

Required scope: specs:read

Parameter	Type	Required	Description
`specId`	string	Yes	Public ID (GUID) of the API specification

lint_spec

Validate an API specification against style guide rules. Returns violations grouped by severity (error, warning, info) with rule details and affected paths. Use this to check against style guide rules; to check against the OpenAPI standard use validate_spec. Requires project context.

Required scope: specs:read

Parameter	Type	Required	Description
`specId`	string	Yes	Public ID (GUID) of the API specification to lint

set_versioning_strategy

Set or update the versioning strategy for an API specification. Defines how API versions are transmitted (URL path, header, query param, content negotiation). Use this to change the strategy; to read the current one use get_versioning_strategy. Requires project context.

Required scope: specs:write

Parameter	Type	Required	Description
`specId`	string	Yes	Public ID (GUID) of the API specification
`strategyType`	string	Yes	Strategy type: 'urlPath', 'header', 'queryParam', or 'contentNegotiation'
`parameterName`	string	Yes	Parameter name for the version (e.g., 'v' for URL path, 'Api-Version' for header, 'api-version' for query)
`urlPattern`	string	No	URL pattern for urlPath strategy (e.g., '/v{major}'). Only required for urlPath.
`defaultBehavior`	string	No (default `"latest"`)	Default behavior when no version is specified: 'latest' (default), 'specific', or 'requireExplicit'
`strictMode`	boolean	No (default `false`)	If true, reject requests without explicit version identifier (default false)