appd_get_anomaly_violations

Retrieve anomaly violations for an application within a time window. Set fetchSuspectedCause=true to include the suspected-cause RCA payload (eventDetailMap.{id}.suspectedCauses[]).

Server Appd jagalliers/appd-mcp
Category Read
Risk class Low
Parameters 00 required

What appd_get_anomaly_violations does on Appd

AI agents call appd_get_anomaly_violations 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.

Why appd_get_anomaly_violations needs a policy

This tool retrieves anomaly violation data and diagnostics (suspected causes) from AppDynamics for monitoring and analysis purposes. It performs a passive query operation with no side effects, data modifications, or external executions. The read-only nature of the server and the retrieval-only semantics classify this as a Read operation with low severity due to limited blast radius if misused.

From the tool's definition Tool name contains 'get' and description uses 'Retrieve'; server is described as 'read-only MCP server' with 'query' operations; no data modification, deletion, execution, or financial operations involved.

Questions about appd_get_anomaly_violations

What does the appd_get_anomaly_violations tool do? +

Retrieve anomaly violations for an application within a time window. Set fetchSuspectedCause=true to include the suspected-cause RCA payload (eventDetailMap.{id}.suspectedCauses[]). It is categorised as a Read tool in the Appd MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on appd_get_anomaly_violations? +

Register the Appd MCP server in PolicyLayer and add a rule for appd_get_anomaly_violations: 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.

What risk level is appd_get_anomaly_violations? +

appd_get_anomaly_violations is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit appd_get_anomaly_violations? +

Yes. Add a rate_limit block to the appd_get_anomaly_violations 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.

How do I block appd_get_anomaly_violations completely? +

Set action: deny in the PolicyLayer policy for appd_get_anomaly_violations. 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.

What MCP server provides appd_get_anomaly_violations? +

appd_get_anomaly_violations 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.