List all available documentation sets in DevDocs
AI agents call list_devdocs_available to retrieve information from MCP Developer 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 enumerates available documentation sources without modifying, executing, or deleting anything. It is a pure read operation with minimal security risk—even if misused by an agent, the worst outcome would be information disclosure of what documentation is available, which is typically non-sensitive. The tool performs no code execution, state changes, or resource destruction.
From the tool's definition Tool name 'list_devdocs_available' and description 'List all available documentation sets' indicate a simple listing/query operation with no side effects.
Attacks that exploit this kind of access
List all available documentation sets in DevDocs. It is categorised as a Read tool in the MCP Developer Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Developer Server MCP server in PolicyLayer and add a rule for list_devdocs_available: 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 MCP Developer Server. Nothing to install.
list_devdocs_available 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 list_devdocs_available 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 list_devdocs_available. 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.
list_devdocs_available is provided by the MCP Developer Server MCP server (ra86-dev/mcpdockershell). 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 →