AI agents call identity_get_token_vault as a supporting operation in Prometheus MCP Server workflows.
The name suggests retrieving tokens from a vault, which could be a Read operation, but without a description it's unclear. 'Get token' implies reading/fetching credentials, but could also involve authentication side-effects. Given the empty description, confidence is low and severity is medium due to potential credential exposure risk.
From the tool's definition Tool name is 'identity_get_token_vault' but description is empty or uninformative.
Documented attack patterns abuse exactly the kind of access identity_get_token_vault gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Prometheus MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for identity_get_token_vault:
{
"version": "1",
"default": "deny",
"tools": {
"identity_get_token_vault": {
"limits": [
{
"counter": "identity_get_token_vault_rate",
"window": "minute",
"max": 60,
"scope": "grant"
}
]
}
}
} identity_get_token_vault gets a rate cap, and everything else on the server is denied unless you say otherwise.
Free to start. No card required.
identity_get_token_vault. It is categorised as a Other tool in the Prometheus MCP Server MCP Server, which means it performs auxiliary operations.
Register the Prometheus MCP Server MCP server in PolicyLayer and add a rule for identity_get_token_vault: 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 Prometheus MCP Server. Nothing to install.
identity_get_token_vault is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the identity_get_token_vault 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 identity_get_token_vault. 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.
identity_get_token_vault is provided by the Prometheus MCP Server MCP server (awslabs.prometheus-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Prometheus MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
805 Prometheus MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.