AI agents call get_delivery_slots to retrieve information from Rohlik without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves delivery time slot availability—a read-only operation with no side effects. It queries existing data about delivery options for the user's address but does not create, modify, delete, or execute any actions. While it accesses user-specific information (address context), it does not expose financial data or enable transactions.
From the tool's definition Tool name 'get_delivery_slots' and description 'Get available delivery time slots for your address' indicate a query operation that retrieves scheduling information without modifying any data.
Attacks that exploit this kind of access
Get available delivery time slots for your address. It is categorised as a Read tool in the Rohlik MCP Server, which means it retrieves data without modifying state.
Register the Rohlik MCP server in PolicyLayer and add a rule for get_delivery_slots: 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 Rohlik. Nothing to install.
get_delivery_slots 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_delivery_slots 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_delivery_slots. 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_delivery_slots is provided by the Rohlik MCP server (@tomaspavlin/rohlik-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
get_delivery_slots is one line of Rohlik's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →