AI agents call mcp_get_dependencies to retrieve information from Mcpql without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves dependency information (which objects reference or depend on a given database object) — a read-only metadata query with no side effects. It does not execute arbitrary queries, modify data, delete objects, or trigger external operations. The low severity reflects minimal blast radius even if misused by an AI agent, as it only exposes database schema structure information.
From the tool's definition Tool name 'mcp_get_dependencies' and description 'Get dependencies for a database object' indicate a query/retrieval operation that reads metadata about object relationships without modifying, deleting, or executing code.
Attacks that exploit this kind of access
Get dependencies for a database object (tables, views, stored procedures, etc.). It is categorised as a Read tool in the Mcpql MCP Server, which means it retrieves data without modifying state.
Register the Mcpql MCP server in PolicyLayer and add a rule for mcp_get_dependencies: 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 Mcpql. Nothing to install.
mcp_get_dependencies 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 mcp_get_dependencies 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 mcp_get_dependencies. 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.
mcp_get_dependencies is provided by the Mcpql MCP server (mcpql). 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 →