Apply a workflow Decision to a content item (POST /v3/accounts/{account_id}/users/{user_id}/content/{content_id}/decisions). Content-level decisions target one piece of user-generated content — typical for content_abuse abuse type (e.g. take-down a listing flagged as scam). Requires SIFT_ACCOUNT_ID.
AI agents use apply_decision_to_content 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 is a Write operation—it modifies the state of content items reversibly (decisions can presumably be appealed/reversed, as suggested by the mention of 'accept_dispute' as a sibling tool). While it has policy enforcement purposes, it directly alters content status without permanent deletion.
From the tool's definition Tool applies a workflow Decision to content (POST operation), performing actions like take-down on user-generated content flagged for abuse. The description explicitly mentions 'take-down' which modifies content visibility/status.
Documented attack patterns abuse exactly the kind of access apply_decision_to_content 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 apply_decision_to_content:
{
"version": "1",
"default": "deny",
"tools": {
"apply_decision_to_content": {
"limits": [
{
"counter": "apply_decision_to_content_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}apply_decision_to_content 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.
Apply a workflow Decision to a content item (POST /v3/accounts/{account_id}/users/{user_id}/content/{content_id}/decisions). Content-level decisions target one piece of user-generated content — typical for content_abuse abuse type (e.g. take-down a listing flagged as scam). Requires SIFT_ACCOUNT_ID. 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 apply_decision_to_content: 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.
apply_decision_to_content 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 apply_decision_to_content 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 apply_decision_to_content. 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.
apply_decision_to_content 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.