Approve or reject a review queue pair
Part of the GoldenMatch server.
Free to start. No card required.
AI agents use agent_approve_reject to create or modify resources in GoldenMatch. 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 agent_approve_reject 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 GoldenMatch.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"agent_approve_reject": {
"limits": [
{
"counter": "agent_approve_reject_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full GoldenMatch policy for all 42 tools.
These attack patterns abuse exactly the kind of access agent_approve_reject 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.
Approve or reject a review queue pair. It is categorised as a Write tool in the GoldenMatch MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the GoldenMatch MCP server in PolicyLayer and add a rule for agent_approve_reject: 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 GoldenMatch. Nothing to install.
agent_approve_reject 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 agent_approve_reject 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 agent_approve_reject. 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.
agent_approve_reject is provided by the GoldenMatch MCP server (pypi:goldenmatch). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 42 GoldenMatch 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.