Remove the cover image from a conference.
AI agents call delete_conference_cover_image to permanently remove resources in Confd — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool performs an irreversible deletion operation on a conference's cover image. While not as critical as deleting entire records, this is a destructive action that cannot be undone and represents data loss. It belongs in the Destructive category rather than Write, as the operation is permanent and not reversible through normal update mechanisms.
From the tool's definition Tool name contains 'delete' and description states 'Remove the cover image from a conference' — this irreversibly deletes a media asset without reversal capability.
Attacks that exploit this kind of access
Remove the cover image from a conference. It is categorised as a Destructive tool in the Confd MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Confd MCP server in PolicyLayer and add a rule for delete_conference_cover_image: 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 Confd. Nothing to install.
delete_conference_cover_image 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 delete_conference_cover_image 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 delete_conference_cover_image. 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.
delete_conference_cover_image is provided by the Confd MCP server (mytours/confd-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →