Trace Magento execution flow from an entry point (route, API endpoint, GraphQL mutation, event, or cron job). Chains multiple searches to map controller → plugins → observers → templates for a given request path. Use this to understand how a request is processed end-to-end.
AI agents call magento_trace_flow to retrieve information from Magector without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
magento_trace_flow is a semantic code analysis tool that retrieves and correlates existing code structure (controllers, plugins, observers, templates) to visualize execution paths. It has no side effects, cannot modify state, and does not execute code or trigger external operations. This is purely a Read operation — querying and analyzing Magento's codebase to produce understanding of flow.
From the tool's definition Tool performs 'Trace Magento execution flow', 'Chains multiple searches to map', and 'understand how a request is processed' — these are query and analysis operations with no modifications.
Attacks that exploit this kind of access
Trace Magento execution flow from an entry point (route, API endpoint, GraphQL mutation, event, or cron job). Chains multiple searches to map controller → plugins → observers → templates for a given request path. Use this to understand how a request is processed end-to-end. It is categorised as a Read tool in the Magector MCP Server, which means it retrieves data without modifying state.
Register the Magector MCP server in PolicyLayer and add a rule for magento_trace_flow: 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 Magector. Nothing to install.
magento_trace_flow 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 magento_trace_flow 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 magento_trace_flow. 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.
magento_trace_flow is provided by the Magector MCP server (magector). 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 →