list_documentations
AI agents call list_documentations to retrieve information from DevDocs 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 or enumerates available documentation metadata without modifying, executing, or deleting anything. It has no side effects and fits the Read category. Severity is low because the blast radius of misuse is minimal—an AI agent listing available documentation cannot cause harm. Confidence is slightly reduced (0.85 vs higher) due to the empty description, though the name and context are clear enough.
From the tool's definition Tool name 'list_documentations' indicates a listing/enumeration operation. No description provided, but the sibling tools (get_documentation_index, get_page_content, search_across_docs, export_documentation) and server context confirm this is a documentation…
Attacks that exploit this kind of access
list_documentations. It is categorised as a Read tool in the DevDocs MCP Server MCP Server, which means it retrieves data without modifying state.
Register the DevDocs MCP Server MCP server in PolicyLayer and add a rule for list_documentations: 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 DevDocs MCP Server. Nothing to install.
list_documentations 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_documentations 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_documentations. 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_documentations is provided by the DevDocs MCP Server MCP server (javierdevcol/devdocs-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 →