list_reconciliation_rejections
AI agents call list_reconciliation_rejections 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 tool performs a retrieval/query operation to list rejections from a reconciliation process. Despite the empty description reducing confidence slightly, the naming convention and the context of a security posture management platform indicate this retrieves historical or status information rather than modifying, executing, or destructively acting on data.
From the tool's definition Tool name 'list_reconciliation_rejections' uses the verb 'list', which is a read operation that retrieves data without modifying it.
Attacks that exploit this kind of access
list_reconciliation_rejections. 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 list_reconciliation_rejections: 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.
list_reconciliation_rejections 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_reconciliation_rejections 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_reconciliation_rejections. 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_reconciliation_rejections 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 →