AI agents call gists_delete to permanently remove resources in TypeSpec MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deletion of gists constitutes destructive action as it permanently removes data. Although gists may not be mission-critical infrastructure, the irreversible nature of deletion and potential loss of code/documentation places this in the Destructive category rather than Write. High severity reflects the blast radius of accidental or malicious deletion of user gists.
From the tool's definition Tool name 'gists_delete' and description 'Delete a gist' explicitly perform deletion, which is an irreversible operation that cannot be undone.
Documented attack patterns abuse exactly the kind of access gists_delete gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and TypeSpec MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for gists_delete:
{
"version": "1",
"default": "deny",
"hide": [
"gists_delete"
]
} gists_delete 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 a gist. It is categorised as a Destructive tool in the TypeSpec MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the TypeSpec MCP Server MCP server in PolicyLayer and add a rule for gists_delete: 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 TypeSpec MCP Server. Nothing to install.
gists_delete 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 gists_delete 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 gists_delete. 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.
gists_delete is provided by the TypeSpec MCP Server MCP server (microsoft/typespec-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from TypeSpec 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.
28 TypeSpec MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.