プロジェクトチケットを削除します
AI agents call delete_project_ticket to permanently remove resources in hokan MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently deletes data without the ability to undo the action. Deletion operations that cannot be reversed are classified as Destructive, the most severe category among non-financial operations. The high severity reflects the risk that an AI agent could inadvertently delete important project management records, disrupting workflow and losing information.
From the tool's definition Tool name is 'delete_project_ticket' and description states 'プロジェクトチケットを削除します' (delete project ticket). The function irreversibly removes a project ticket record from the system.
Attacks that exploit this kind of access
プロジェクトチケットを削除します. It is categorised as a Destructive tool in the hokan MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the hokan MCP Server MCP server in PolicyLayer and add a rule for delete_project_ticket: 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 hokan MCP Server. Nothing to install.
delete_project_ticket 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_project_ticket 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_project_ticket. 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_project_ticket is provided by the hokan MCP Server MCP server (shinonft/hokan-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 →