Get detailed information about a specific application.
AI agents call get_application to retrieve information from Mcp Read Only Argocd without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves application metadata and configuration from Argo CD without modifying any state. It is a query operation consistent with the read-only nature of the server. Misuse by an AI agent could expose sensitive application details but poses no destructive or financial risk, warranting a 'low' severity classification.
From the tool's definition Tool is named 'get_application' with description stating it 'Get[s] detailed information about a specific application.' The server is explicitly described as 'read-only' with tools limited to querying (list_, get_) operations.
Attacks that exploit this kind of access
Get detailed information about a specific application. It is categorised as a Read tool in the Mcp Read Only Argocd MCP Server, which means it retrieves data without modifying state.
Register the Mcp Read Only Argocd MCP server in PolicyLayer and add a rule for get_application: 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 Mcp Read Only Argocd. Nothing to install.
get_application 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_application 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_application. 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_application is provided by the Mcp Read Only Argocd MCP server (lukleh/mcp-read-only-argocd). 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 →