Get Backstage API reference including REST endpoints, GraphQL, and client libraries
AI agents call get_api_reference to retrieve information from Backstage MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries existing API reference documentation. It performs a read-only operation to fetch information about endpoints, GraphQL schemas, and client library documentation. There is no data modification, code execution, deletion, or financial impact. The blast radius of misuse is minimal—an agent could only access publicly documented API information.
From the tool's definition Tool name 'get_api_reference' and description 'Get Backstage API reference including REST endpoints, GraphQL, and client libraries' indicates retrieval of documentation/reference material with no side effects.
Attacks that exploit this kind of access
Get Backstage API reference including REST endpoints, GraphQL, and client libraries. It is categorised as a Read tool in the Backstage MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Backstage MCP Server MCP server in PolicyLayer and add a rule for get_api_reference: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Backstage MCP Server. Nothing to install.
get_api_reference is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_api_reference rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for get_api_reference. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
get_api_reference is provided by the Backstage MCP Server MCP server (pawelwaj/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →