get_effective_coverage
AI agents call get_effective_coverage to retrieve information from Mipiti MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'get_' prefix and the sibling context (add_* tools for creating/modifying security artifacts) strongly suggest this tool retrieves or queries existing coverage data. No keywords indicating modification, deletion, code execution, or financial operations are present. Low severity due to read-only nature—misuse would only expose information, not alter system state.
From the tool's definition Tool name 'get_effective_coverage' indicates a query or retrieval operation (getter pattern). No description provided, but the verb 'get' combined with the context of a security posture platform suggests fetching computed or aggregated coverage metrics…
Attacks that exploit this kind of access
get_effective_coverage. It is categorised as a Read tool in the Mipiti MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Mipiti MCP Server MCP server in PolicyLayer and add a rule for get_effective_coverage: 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 Mipiti MCP Server. Nothing to install.
get_effective_coverage 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_effective_coverage 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_effective_coverage. 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_effective_coverage is provided by the Mipiti MCP Server MCP server (mipiti/mipiti-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 →