Get application endpoints for connectivity templates in a blueprint
AI agents call get_app_ep 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 queries and retrieves application endpoint information without side effects. No data is created, modified, deleted, or executed. It is a straightforward read operation on a datacenter network blueprint configuration. The blast radius of misuse is minimal—exposing network endpoint information carries informational risk only.
From the tool's definition Tool name 'get_app_ep' and description 'Get application endpoints' use retrieval language (get). The description contains no modification, deletion, execution, or financial keywords.
Attacks that exploit this kind of access
Get application endpoints for connectivity templates in 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_app_ep: 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_app_ep 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_app_ep 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_app_ep. 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_app_ep 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 →