AI agents call get_component_docs to retrieve information from MCP Modus without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a documentation lookup tool that queries and returns information about web components without side effects. It performs a retrieval operation typical of a Read category tool. Even in a compromised agent scenario, returning documentation poses minimal risk—the worst case is retrieving incorrect or misleading documentation, which would be caught during development.
From the tool's definition Tool description explicitly states it 'Get[s] the complete documentation' with no indication of modification, deletion, or execution capabilities. The method retrieves component documentation (attributes, events, usage examples) in read-only fashion.
Attacks that exploit this kind of access
Get the complete documentation for a specific Modus Web Component including attributes, events, and usage examples. It is categorised as a Read tool in the MCP Modus MCP Server, which means it retrieves data without modifying state.
Register the MCP Modus MCP server in PolicyLayer and add a rule for get_component_docs: 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 Modus. Nothing to install.
get_component_docs 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_component_docs 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_component_docs. 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_component_docs is provided by the MCP Modus MCP server (julianoczkowski/mcp-modus). 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 →