apstra_list_anomalies

List anomalies for one Apstra blueprint with compact health fields.

SERVERAPI-Central SOURCEsecure-ssid/centralmcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/secure-ssid-centralmcp/apstra-list-anomalies.md

WHAT IT DOES

What apstra_list_anomalies does on API-Central

AI agents call apstra_list_anomalies to retrieve information from API-Central without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why apstra_list_anomalies is rated Low

This tool retrieves and lists anomalies from an Apstra blueprint, returning health status information. The verb 'list' combined with the read-only nature of querying anomalies (no side effects, no state changes) places this firmly in the Read category.

From the tool's definition Tool name 'apstra_list_anomalies' and description 'List anomalies' indicates a query/retrieval operation with no modification of data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs apstra_list_anomalies safely

PolicyLayer is an MCP gateway: it sits between your AI agents and API-Central, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For apstra_list_anomalies, this is the rule to start with:

apstra_list_anomalies Allowed

apstra_list_anomalies is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "apstra_list_anomalies": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect API-Central, apply this rule, and every apstra_list_anomalies call is checked against it from then on.

FAQ

Questions about apstra_list_anomalies

What does the apstra_list_anomalies tool do? +

List anomalies for one Apstra blueprint with compact health fields. It is categorised as a Read tool in the API-Central MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on apstra_list_anomalies? +

Register the API-Central MCP server in PolicyLayer and add a rule for apstra_list_anomalies: 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 API-Central. Nothing to install.

What risk level is apstra_list_anomalies? +

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

Can I rate-limit apstra_list_anomalies? +

Yes. Add a rate_limit block to the apstra_list_anomalies 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 apstra_list_anomalies completely? +

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

apstra_list_anomalies is provided by the API-Central MCP server (secure-ssid/centralmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on API-Central, and thousands of servers like it.

This server

All 590 API-Central tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →