AI agents call store_get to retrieve information from Willow without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves data by ID from storage without side effects. It is a straightforward query/fetch operation that poses minimal risk even if misused by an agent, as it only returns existing data. The mention of SAP/1.0 authorization provides additional security controls but does not change the fundamental nature of the operation.
From the tool's definition Tool description states 'Read a single record by ID from a collection. Returns the full record object' — explicitly a read operation with no modification or deletion.
Attacks that exploit this kind of access
Read a single record by ID from a collection. Returns the full record object, or {error: not_found} if missing. It is categorised as a Read tool in the Willow MCP Server, which means it retrieves data without modifying state.
Register the Willow MCP server in PolicyLayer and add a rule for store_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 Willow. Nothing to install.
store_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 store_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 store_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.
store_get is provided by the Willow MCP server (rudi193-cmd/willow-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →