This record as markdown: /tools/108yen-memo-mcp/deletecategory.md
What deleteCategory does on Memo
AI agents call deleteCategory to permanently remove resources in Memo, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why deleteCategory is rated Critical
This tool permanently removes a category from the memo database. Deletion is irreversible and cannot be undone without manual intervention or backups. The impact is high because deleting a category may cascade effects on associated memos or application logic that depends on that category.
From the tool's definition Tool name is 'deleteCategory' and description states 'Delete a category'. The verb 'delete' combined with action on a stored category indicates irreversible removal of data.
Attacks that exploit this kind of access
The rule that runs deleteCategory safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Memo, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For deleteCategory, this is the rule to start with:
deleteCategory is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Memo, apply this rule, and every deleteCategory call is checked against it from then on.
Questions about deleteCategory
Delete a category. It is categorised as a Destructive tool in the Memo MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Memo MCP server in PolicyLayer and add a rule for deleteCategory: 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 Memo. Nothing to install.
deleteCategory 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 deleteCategory 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 deleteCategory. 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.
deleteCategory is provided by the Memo MCP server (108yen/memo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Memo, and thousands of servers like it.
Across the catalogue