Merge a museum into another museum. The source museum (id) will have its merged_into_id set and be discarded. The target museum (merged_into_id) remains unchanged. Returns the updated source museum record.
AI agents call merge_museum 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.
Merging discards the source museum record irreversibly. While the data may technically persist with a merged_into_id marker, the source museum is effectively removed from active use and cannot be recovered as a standalone entity. This constitutes an irreversible destructive action with high blast radius if misused on the wrong museum.
From the tool's definition 'The source museum (id) will have its merged_into_id set and be discarded' — the source museum is permanently discarded/deactivated as a result of the merge operation, which is irreversible.
Attacks that exploit this kind of access
Merge a museum into another museum. The source museum (id) will have its merged_into_id set and be discarded. The target museum (merged_into_id) remains unchanged. Returns the updated source museum record. 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 merge_museum: 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.
merge_museum 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 merge_museum 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 merge_museum. 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.
merge_museum 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 →