reject_reconciliation_candidate
AI agents use reject_reconciliation_candidate to create or update resources in Mipiti MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mipiti MCP Server environment.
The tool performs a reversible modification operation—rejecting a candidate reconciliation entry. This is a Write action because it updates platform state (marking a candidate as rejected) without permanently destroying data or executing arbitrary code.
From the tool's definition Tool name 'reject_reconciliation_candidate' indicates a state-change action (rejection) on reconciliation data. The Mipiti platform manages security posture models, and rejection of a reconciliation candidate modifies tracked state reversibly.
Attacks that exploit this kind of access
reject_reconciliation_candidate. It is categorised as a Write tool in the Mipiti MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mipiti MCP Server MCP server in PolicyLayer and add a rule for reject_reconciliation_candidate: 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.
reject_reconciliation_candidate is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the reject_reconciliation_candidate 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 reject_reconciliation_candidate. 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.
reject_reconciliation_candidate 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 →