AI agents call get to retrieve information from ClawMem without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a simple retrieval operation on stored documents. It fetches data based on an identifier (file path or docid) without any side effects, modification, or irreversible actions. The blast radius of misuse is minimal—an agent could retrieve documents it shouldn't access, but cannot modify, delete, or execute operations. This is a straightforward Read category tool with low severity.
From the tool's definition Tool name 'get' and description 'Retrieve document by file path or docid' clearly indicates data retrieval with no modification or deletion capability.
Documented attack patterns abuse exactly the kind of access get gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and ClawMem, and nothing reaches the server without passing your rules. This is the rule we recommend for get:
{
"version": "1",
"default": "deny",
"tools": {
"get": {}
}
}get is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Retrieve document by file path or docid. It is categorised as a Read tool in the ClawMem MCP Server, which means it retrieves data without modifying state.
Register the ClawMem MCP server in PolicyLayer and add a rule for get: 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 ClawMem. Nothing to install.
get 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 get 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 get. 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.
get is provided by the ClawMem MCP server (yoloshii/clawmem). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 30 ClawMem tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
30 ClawMem tools catalogued and risk-classified — across an index of 42,500+ MCP servers.