Get configuration diff status for a blueprint
AI agents call get_diff_status to retrieve information from Apstra MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves status information about configuration differences in a blueprint. The verb 'Get' and the absence of any modification, execution, or destructive language clearly place this in the Read category. The blast radius is minimal since it only returns status information that would inform decisions but does not execute changes or trigger deployment actions.
From the tool's definition Tool name 'get_diff_status' and description 'Get configuration diff status for a blueprint' indicate a retrieval operation that queries the state of configuration differences without modifying, executing, or deleting anything.
Attacks that exploit this kind of access
Get configuration diff status for a blueprint. It is categorised as a Read tool in the Apstra MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Apstra MCP Server MCP server in PolicyLayer and add a rule for get_diff_status: 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 Apstra MCP Server. Nothing to install.
get_diff_status 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_diff_status 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_diff_status. 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_diff_status is provided by the Apstra MCP Server MCP server (vignitin/apstra-mcp-server). 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 →