delete_profile
AI agents call delete_profile to permanently remove resources in Mcp Director — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deletion operations fall under the Destructive category as they permanently remove data. In the context of MCP profile management, deleting a profile removes stored configuration settings. This is rated 'high' severity because an AI agent could accidentally or maliciously delete critical profiles needed for task execution, disrupting the user's workflow and requiring manual reconfiguration to recover.
From the tool's definition The tool name 'delete_profile' clearly indicates irreversible deletion of a profile configuration. While the description is empty, the function name unambiguously implies data removal that cannot be undone.
Attacks that exploit this kind of access
delete_profile. It is categorised as a Destructive tool in the Mcp Director MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mcp Director MCP server in PolicyLayer and add a rule for delete_profile: 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 Director. Nothing to install.
delete_profile 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_profile 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_profile. 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_profile is provided by the Mcp Director MCP server (yut0takagi/mcp-director). 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 →