storage_set_local
A write tool on the Mcp Anything MCP server.
This record as markdown: /tools/mcp-anything/storage-set-local.md
What storage_set_local does on Mcp Anything
AI agents use storage_set_local to create or update resources in Mcp Anything, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Anything environment.
Why storage_set_local is rated Medium
The tool name strongly suggests writing data to local storage. With an empty description, confidence is reduced but the 'set' operation clearly modifies state rather than reading it. Severity is high because local storage manipulation could affect application state, configuration, or user data, though without destructive deletion semantics.
From the tool's definition Tool name 'storage_set_local' indicates setting/writing to local storage. The 'set' verb implies modification of data.
Attacks that exploit this kind of access
The rule that runs storage_set_local safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Anything, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For storage_set_local, this is the rule to start with:
storage_set_local 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 Mcp Anything, apply this rule, and every storage_set_local call is checked against it from then on.
Questions about storage_set_local
storage_set_local is a write tool on the Mcp Anything MCP server. It is categorised as a Write tool in the Mcp Anything MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Anything MCP server in PolicyLayer and add a rule for storage_set_local: 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 Mcp Anything. Nothing to install.
storage_set_local 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 storage_set_local 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 storage_set_local. 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.
storage_set_local is provided by the Mcp Anything MCP server (Zaymadkid/mcp-anything). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Anything, and thousands of servers like it.
This server
Across the catalogue