This record as markdown: /tools/108yen-memo-mcp/createcategory.md
What createCategory does on Memo
AI agents use createCategory 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 createCategory is rated Medium
This tool creates new data (a category) in the local memo database, which is reversible and has no side effects beyond the database itself. It fits the Write category as it creates data without destruction or external execution. Severity is low because creating a category has minimal blast radius—it doesn't affect existing data, financial systems, or trigger external operations.
From the tool's definition Tool name 'createCategory' and description 'Create a new category' indicate a data creation operation that modifies the memo database by adding a new category entry.
Attacks that exploit this kind of access
The rule that runs createCategory 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 createCategory, this is the rule to start with:
createCategory 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 createCategory call is checked against it from then on.
Questions about createCategory
Create a new 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 createCategory: 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.
createCategory 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 createCategory 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 createCategory. 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.
createCategory 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