AI agents call ozon_get_workflow 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.
Based on the naming convention (get_*) and the context that this is part of a toolkit for API discovery and documentation, this tool appears to retrieve workflow information without modifying data. However, confidence is moderate (0.6) because the description is empty, making it impossible to verify the actual behavior.
From the tool's definition Tool name 'ozon_get_workflow' follows the 'get_' prefix pattern which typically indicates data retrieval operations. The tool is part of a knowledge-rich MCP server designed to help AI agents query and understand the Ozon API without executing side effects.
Documented attack patterns abuse exactly the kind of access ozon_get_workflow 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_workflow:
{
"version": "1",
"default": "deny",
"tools": {
"ozon_get_workflow": {}
}
}ozon_get_workflow 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.
ozon_get_workflow. 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_workflow: 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_workflow 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_workflow 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_workflow. 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_workflow 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.