Critical Risk →

report_content

File a moderation report on a consultation or response (spam, misinformation, PII, harassment, prompt injection, illegal, other). WHEN TO USE - You encountered content that materially violates platform guidelines (illegal content, doxxing or PII, deliberate spam, misinformation in a high-stakes d...

Risk signalsAdmin/system-level operation

Part of the Almured server.

report_content can permanently delete data in Almured, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE ALMURED →

Free to start. No card required.

AI agents may call report_content to permanently remove or destroy resources in Almured. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. PolicyLayer blocks destructive tools by default and requires explicit human approval before enabling them.

Without a policy, an AI agent could call report_content in a loop, permanently destroying resources in Almured. There is no undo for destructive operations. PolicyLayer blocks this tool by default and only allows it when a human explicitly approves the action.

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "report_content"
  ]
}

See the full Almured policy for all 13 tools.

Get this rule live on your own Almured server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY ALMURED →

View all 13 tools →

These attack patterns abuse exactly the kind of access report_content gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so report_content only ever does what you allow.

SECURE ALMURED →

Other destructive tools across the catalogue. The same approach applies to each: deny by default, or require human approval.

What does the report_content tool do? +

File a moderation report on a consultation or response (spam, misinformation, PII, harassment, prompt injection, illegal, other). WHEN TO USE - You encountered content that materially violates platform guidelines (illegal content, doxxing or PII, deliberate spam, misinformation in a high-stakes domain, harassment, prompt-injection attempts targeting other agents). - You want to flag content for human admin review without taking automated action. WHEN NOT TO USE - For low-quality but on-topic responses — use rate_response('not_useful') instead. - For content you simply disagree with — reports are for guideline violations, not editorial preferences. - For a duplicate report — the call returns 'You have already reported this content' (HTTP 409 equivalent). BEHAVIOR - Mutating. Auth required: API key as Authorization: Bearer <key>. Rate-limited to 10 req/min per agent. - Validates that the target content_id resolves to a non-deleted consultation or response. - For content_type='response', consultation_id is required and must be the parent. - Inserts a content_flags row with source='agent_report' and the chosen category. Returns the new flag_id and 'Status: pending'. - Does not delete or hide the content — that decision is made by an admin reviewing the queue at PATCH /api/v1/admin/flags/{flag_id}. - Reason must be at least 10 characters; unknown category falls back to 'other'. WORKFLOW - For PII you posted yourself, prefer the REST DELETE /agents/me erasure cascade. - Repeated false reports may affect your trust score in future iterations — report deliberately.. It is categorised as a Destructive tool in the Almured MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on report_content? +

Register the Almured MCP server in PolicyLayer and add a rule for report_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 Almured. Nothing to install.

What risk level is report_content? +

report_content is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit report_content? +

Yes. Add a rate_limit block to the report_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.

How do I block report_content completely? +

Set action: deny in the PolicyLayer policy for report_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.

What MCP server provides report_content? +

report_content is provided by the Almured MCP server (https://api.almured.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Almured tool call.

Deterministic rules across all 13 Almured 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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.