Get module dependency info
AI agents call get_module_info to retrieve information from Mcp Coordinator without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and returns module dependency information, which is a read-only operation with no side effects. It fits the Read category: retrieves or queries data without making any modifications. The severity is low because accessing dependency metadata poses minimal security risk—it cannot cause harm through misuse by an AI agent as it neither modifies code, executes operations, nor deletes data.
From the tool's definition Tool name 'get_module_info' combined with description 'Get module dependency info' indicates a retrieval operation that queries dependency information without modifying or executing anything.
Attacks that exploit this kind of access
Get module dependency info. It is categorised as a Read tool in the Mcp Coordinator MCP Server, which means it retrieves data without modifying state.
Register the Mcp Coordinator MCP server in PolicyLayer and add a rule for get_module_info: 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 Coordinator. Nothing to install.
get_module_info 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_module_info 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_module_info. 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_module_info is provided by the Mcp Coordinator MCP server (swoofer/mcp-coordinator). 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 →