Report how a confirmed match went. Available after both parties accepted and contact info was revealed. Outcomes: - 'succeeded': Found the right person. Mandate closes. - 'failed': Didn't work out. Mandate reactivates for new matches. - 'ongoing': Still in conversation. OpenMandate checks back la...
Part of the OpenMandate server.
Free to start. No card required.
AI agents use openmandate_submit_outcome to create or modify resources in OpenMandate. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call openmandate_submit_outcome repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach OpenMandate.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"openmandate_submit_outcome": {
"limits": [
{
"counter": "openmandate_submit_outcome_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full OpenMandate policy for all 15 tools.
These attack patterns abuse exactly the kind of access openmandate_submit_outcome gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Report how a confirmed match went. Available after both parties accepted and contact info was revealed. Outcomes: - 'succeeded': Found the right person. Mandate closes. - 'failed': Didn't work out. Mandate reactivates for new matches. - 'ongoing': Still in conversation. OpenMandate checks back later. IMPORTANT: Always confirm the outcome with the user before submitting. This affects their mandate and matching status.. It is categorised as a Write tool in the OpenMandate MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the OpenMandate MCP server in PolicyLayer and add a rule for openmandate_submit_outcome: 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 OpenMandate. Nothing to install.
openmandate_submit_outcome 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 openmandate_submit_outcome 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 openmandate_submit_outcome. 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.
openmandate_submit_outcome is provided by the OpenMandate MCP server (https://mcp.openmandate.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 15 OpenMandate tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.