This record as markdown: /tools/108yen-memo-mcp/getcategory.md
What getCategory does on Memo
AI agents call getCategory to retrieve information from Memo without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why getCategory is rated Low
This tool retrieves a single category record from the memo database by its ID. It has no side effects, does not modify or delete data, and does not execute external operations. This is a straightforward read operation with minimal blast radius if misused by an agent.
From the tool's definition Tool name is 'getCategory' and description states 'Get a single category by ID' — both indicate a retrieval operation with no modification or deletion.
Attacks that exploit this kind of access
The rule that runs getCategory 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 getCategory, this is the rule to start with:
getCategory is read-only, so it stays allowed. 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 getCategory call is checked against it from then on.
Questions about getCategory
Get a single category by ID. It is categorised as a Read tool in the Memo MCP Server, which means it retrieves data without modifying state.
Register the Memo MCP server in PolicyLayer and add a rule for getCategory: 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.
getCategory is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the getCategory 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 getCategory. 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.
getCategory 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