Analyze dependencies for a database object. Shows what it references and what references it.
AI agents call get_dependencies to retrieve information from MSSQL MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns dependency information about database objects. It performs analysis of existing schema metadata—specifically which objects reference others and vice versa. This is a pure Read operation: it has no side effects, does not execute business logic, does not modify any data, and does not trigger external operations.
From the tool's definition Tool name 'get_dependencies' and description 'Analyze dependencies for a database object. Shows what it references and what references it.' indicate a read-only query operation that retrieves metadata about object relationships without modifying data.
Attacks that exploit this kind of access
Analyze dependencies for a database object. Shows what it references and what references it. It is categorised as a Read tool in the MSSQL MCP Server MCP Server, which means it retrieves data without modifying state.
Register the MSSQL MCP Server MCP server in PolicyLayer and add a rule for 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 MSSQL MCP Server. Nothing to install.
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 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 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.
get_dependencies is provided by the MSSQL MCP Server MCP server (jpcanter/sql-server-mcp). 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 →