ブログを削除します
AI agents call verge_delete_blog to permanently remove resources in Verge MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool permanently deletes a blog, which is an irreversible action that destroys data without undo capability. This fits the Destructive category as the primary risk. While it could also be classified as Execute (triggers an external operation), Destructive is more severe and appropriate given the irreversible nature of deletion.
From the tool's definition Tool name 'verge_delete_blog' combined with description 'ブログを削除します' (Japanese: 'Delete a blog') indicates permanent deletion of blog data. This is irreversible data destruction.
Attacks that exploit this kind of access
ブログを削除します. It is categorised as a Destructive tool in the Verge MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Verge MCP Server MCP server in PolicyLayer and add a rule for verge_delete_blog: 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 Verge MCP Server. Nothing to install.
verge_delete_blog 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 verge_delete_blog 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 verge_delete_blog. 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.
verge_delete_blog is provided by the Verge MCP Server MCP server (tomohirof/verge-mcp-server). 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 →