Find XML configuration files and nodes in Magento — di.xml (dependency injection), events.xml (observers), routes.xml (routing), system.xml (admin config), webapi.xml (REST/SOAP), module.xml (module declarations), layout XML. See also: magento_find_observer (events.xml), magento_find_preference (...
AI agents call magento_find_config 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.
This is a semantic code search tool that retrieves and indexes configuration metadata. It does not create, modify, delete, execute, or trigger any side effects — it only locates and returns information about existing configuration structure. The cross-references to sibling tools like magento_find_observer and magento_find_preference reinforce that this family performs read-only analysis.
From the tool's definition Tool description explicitly states it 'Find[s] XML configuration files and nodes' — a search/discovery operation with no modification or execution capability.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
Find XML configuration files and nodes in Magento — di.xml (dependency injection), events.xml (observers), routes.xml (routing), system.xml (admin config), webapi.xml (REST/SOAP), module.xml (module declarations), layout XML. See also: magento_find_observer (events.xml), magento_find_preference (di.xml), magento_find_api (webapi.xml). 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_find_config: 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_find_config 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_find_config 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_find_config. 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_find_config 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 →