Look up Ozon API errors and their solutions.
AI agents call ozon_get_error_catalog to retrieve information from Ozon without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves reference information about API errors and their solutions. It performs a lookup operation similar to consulting documentation or a knowledge base. There is no data creation, modification, deletion, code execution, or financial impact. The primary function is informational—helping users understand error responses. This is a pure Read operation with minimal blast radius if misused by an AI agent.
From the tool's definition Tool name 'ozon_get_error_catalog' and description 'Look up Ozon API errors and their solutions' indicate a retrieval/query operation with no side effects.
Documented attack patterns abuse exactly the kind of access ozon_get_error_catalog gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Ozon, and nothing reaches the server without passing your rules. This is the rule we recommend for ozon_get_error_catalog:
{
"version": "1",
"default": "deny",
"tools": {
"ozon_get_error_catalog": {}
}
}ozon_get_error_catalog is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Look up Ozon API errors and their solutions. It is categorised as a Read tool in the Ozon MCP Server, which means it retrieves data without modifying state.
Register the Ozon MCP server in PolicyLayer and add a rule for ozon_get_error_catalog: 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 Ozon. Nothing to install.
ozon_get_error_catalog 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 ozon_get_error_catalog 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 ozon_get_error_catalog. 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.
ozon_get_error_catalog is provided by the Ozon MCP server (pcdck/ozon-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Ozon, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
15 Ozon tools catalogued and risk-classified — across an index of 43,000+ MCP servers.