Get detailed guide for developing Backstage plugins including setup, structure, and best practices
AI agents call get_plugin_development_guide 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 documentation about Backstage plugin development. It has no side effects on data or systems—it simply returns informational content. This aligns with the Read category definition: 'retrieves or queries data; no side effects.' The low severity reflects that misuse would only result in the AI agent receiving development documentation, posing minimal risk.
From the tool's definition Tool name 'get_plugin_development_guide' and description 'Get detailed guide for developing Backstage plugins' indicate a retrieval operation. The verb 'get' combined with 'guide' clearly signifies fetching documentation or reference material.
Attacks that exploit this kind of access
Get detailed guide for developing Backstage plugins including setup, structure, and best practices. 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_plugin_development_guide: 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_plugin_development_guide 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_plugin_development_guide 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_plugin_development_guide. 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_plugin_development_guide 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 →