Find PHPUnit test files for a given PHP class or method. Searches Test/ directories for test classes, @covers annotations, mock references, and class name matches. Helps identify test coverage for refactoring.
AI agents call magento_find_test 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 tool performs semantic code search within test directories to locate and return information about existing PHPUnit tests. It does not create, modify, delete, execute, or commit any resources. The blast radius of misuse is minimal: an agent could retrieve test metadata it shouldn't see, but cannot alter state or trigger actions. Classified as Read.
From the tool's definition Tool description states it "Searches Test/ directories for test classes" and "Helps identify test coverage" — purely informational queries with no side effects. The verb "Find" and "Searches" indicate read-only retrieval of existing test metadata.
Attacks that exploit this kind of access
Find PHPUnit test files for a given PHP class or method. Searches Test/ directories for test classes, @covers annotations, mock references, and class name matches. Helps identify test coverage for refactoring. 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_test: 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_test 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_test 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_test. 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_test 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 →