Mark an inquiry as declined. Records your final reject decision on the Persona inquiry for reporting and feedback.
AI agents use decline_inquiry to create or update resources in Mcp Ap2 — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Ap2 environment.
This tool writes a decision/status update to an inquiry record (marking it declined). It is reversible in principle (the decision could be changed) and does not delete data, execute code, or move money. The blast radius is medium since declining an inquiry in a payment/authorization protocol context could affect business processes or trust decisions.
From the tool's definition Mark an inquiry as declined. Records your final reject decision on the Persona inquiry for reporting and feedback.
Documented attack patterns abuse exactly the kind of access decline_inquiry gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Ap2, and nothing reaches the server without passing your rules. This is the rule we recommend for decline_inquiry:
{
"version": "1",
"default": "deny",
"tools": {
"decline_inquiry": {
"limits": [
{
"counter": "decline_inquiry_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} decline_inquiry stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Mark an inquiry as declined. Records your final reject decision on the Persona inquiry for reporting and feedback. It is categorised as a Write tool in the Mcp Ap2 MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Ap2 MCP server in PolicyLayer and add a rule for decline_inquiry: 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 Mcp Ap2. Nothing to install.
decline_inquiry 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 decline_inquiry 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 decline_inquiry. 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.
decline_inquiry is provided by the Mcp Ap2 MCP server (@codespar/mcp-ap2). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mcp Ap2, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
1300 Mcp Ap2 tools catalogued and risk-classified — across an index of 43,000+ MCP servers.