Synthesize a tier→tier/backend dependency map from the application model + transaction snapshots (with exit calls). MCP-level aggregation — confidence depends on snapshot density (warning surfaces when sparse).
AI agents call appd_get_dependency_map to retrieve information from Appd without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and aggregates existing AppDynamics data (application model and transaction snapshots) to construct a dependency map visualization. It performs no writes, deletive operations, code execution, or financial actions. The warning about sparse snapshot density is a data-quality caveat, not a side effect.
From the tool's definition Tool name 'appd_get_dependency_map' and description 'Synthesize a tier→tier/backend dependency map from the application model + transaction snapshots' indicate data retrieval and synthesis from existing sources.
Attacks that exploit this kind of access
Synthesize a tier→tier/backend dependency map from the application model + transaction snapshots (with exit calls). MCP-level aggregation — confidence depends on snapshot density (warning surfaces when sparse). It is categorised as a Read tool in the Appd MCP Server, which means it retrieves data without modifying state.
Register the Appd MCP server in PolicyLayer and add a rule for appd_get_dependency_map: 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 Appd. Nothing to install.
appd_get_dependency_map 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 appd_get_dependency_map 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 appd_get_dependency_map. 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.
appd_get_dependency_map is provided by the Appd MCP server (jagalliers/appd-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 →