List configured shops with their last-call status.
AI agents call list_shops to retrieve information from Cz Mtg Compare without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays information about configured shops and their operational status. It has no side effects—it does not create, modify, delete, or execute any operations. It is a pure read operation that returns configuration and status data.
From the tool's definition Tool name 'list_shops' and description 'List configured shops with their last-call status' indicate a query/retrieval operation that returns status information without modifying any data.
Attacks that exploit this kind of access
List configured shops with their last-call status. It is categorised as a Read tool in the Cz Mtg Compare MCP Server, which means it retrieves data without modifying state.
Register the Cz Mtg Compare MCP server in PolicyLayer and add a rule for list_shops: 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 Cz Mtg Compare. Nothing to install.
list_shops 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 list_shops 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 list_shops. 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.
list_shops is provided by the Cz Mtg Compare MCP server (xvyslo05/czech-mtg-price-comparator-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 →