Full Agent Treats store details and pricing.
AI agents call store_info to retrieve information from Agent Treats without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns static information (store details and pricing) without side effects. It is a straightforward read operation that retrieves data. There is no capability to modify inventory, process payments, execute code, or delete anything. Severity is low because misuse poses no meaningful risk—an agent might retrieve pricing information repeatedly, but no harm results.
From the tool's definition Tool name 'store_info' and description 'Full Agent Treats store details and pricing' indicate retrieval of informational content about a store catalog and pricing—no modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
Full Agent Treats store details and pricing. It is categorised as a Read tool in the Agent Treats MCP Server, which means it retrieves data without modifying state.
Register the Agent Treats MCP server in PolicyLayer and add a rule for store_info: 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 Agent Treats. Nothing to install.
store_info 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_info 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_info. 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_info is provided by the Agent Treats MCP server (montecbmd/agent-treats-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 →