This record as markdown: /tools/108yen-memo-mcp/updatecategory.md
What updateCategory does on Memo
AI agents use updateCategory to create or update resources in Memo, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Memo environment.
Why updateCategory is rated Medium
This tool modifies existing category data but does not destroy or permanently delete it. Updates are typically reversible (can be updated again), placing it in the Write category. Severity is medium because misuse could corrupt category organization affecting memo retrieval, but no data is irreversibly lost and no financial impact occurs.
From the tool's definition Tool name is 'updateCategory' and description states 'Update a category', indicating reversible modification of category metadata in the memo database.
Attacks that exploit this kind of access
The rule that runs updateCategory 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 updateCategory, this is the rule to start with:
updateCategory stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Memo, apply this rule, and every updateCategory call is checked against it from then on.
Questions about updateCategory
Update a category. It is categorised as a Write tool in the Memo MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Memo MCP server in PolicyLayer and add a rule for updateCategory: 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.
updateCategory is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the updateCategory 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 updateCategory. 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.
updateCategory 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.
This server
Across the catalogue