Delete an article by moving to the trashed state on the Joomla website, allowing recovery.
AI agents call move_article_to_trash to permanently remove resources in Joomla MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Although the description notes 'allowing recovery,' the tool moves content to a trashed state, which is a destructive action (deletion). The recoverable nature slightly lowers severity from high to medium, but it is still the most severe applicable category since it removes content from active availability and is closer to Destructive than Write.
From the tool's definition 'Delete an article by moving to the trashed state' — explicitly performs a delete action on an article
Documented attack patterns abuse exactly the kind of access move_article_to_trash gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Joomla MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for move_article_to_trash:
{
"version": "1",
"default": "deny",
"hide": [
"move_article_to_trash"
]
} move_article_to_trash disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete an article by moving to the trashed state on the Joomla website, allowing recovery. It is categorised as a Destructive tool in the Joomla MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Joomla MCP Server MCP server in PolicyLayer and add a rule for move_article_to_trash: 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 Joomla MCP Server. Nothing to install.
move_article_to_trash is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the move_article_to_trash 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 move_article_to_trash. 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.
move_article_to_trash is provided by the Joomla MCP Server MCP server (nasoma/joomla-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Joomla MCP Server, 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.
6 Joomla MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.