Find all code that references a database table — across db_schema.xml, Setup scripts (InstallSchema/UpgradeSchema), raw SQL (Zend_Db_Expr, $connection->query), getTable() calls, and resource model definitions. Builds a cross-module dependency map showing who reads/writes/creates a given table. Es...
AI agents call magento_find_table_usage 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 and analysis to identify references to database tables across configuration files and source code. It reads and indexes existing codebase artifacts (db_schema.xml, Setup scripts, SQL expressions, resource models) to build a dependency map.
From the tool's definition Tool description states it 'Find[s] all code that references a database table' and 'Builds a cross-module dependency map' — purely analytical and retrieval-based operations with no modification or execution of code/data.
Attacks that exploit this kind of access
Find all code that references a database table — across db_schema.xml, Setup scripts (InstallSchema/UpgradeSchema), raw SQL (Zend_Db_Expr, $connection->query), getTable() calls, and resource model definitions. Builds a cross-module dependency map showing who reads/writes/creates a given table. Essential for impact analysis of schema changes. 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_table_usage: 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_table_usage 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_table_usage 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_table_usage. 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_table_usage 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 →