Get session metrics (token usage, duration, tool calls).
AI agents call acp_get_session_metrics to retrieve information from Ambient Code Platform 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 and queries session metrics without modifying, executing code, deleting, or causing financial impact. It is a pure read operation on session telemetry data. The blast radius of misuse is minimal—an attacker could observe resource consumption patterns but cannot alter infrastructure or execute operations.
From the tool's definition Tool name 'acp_get_session_metrics' and description 'Get session metrics (token usage, duration, tool calls)' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
Get session metrics (token usage, duration, tool calls). It is categorised as a Read tool in the Ambient Code Platform MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Ambient Code Platform MCP Server MCP server in PolicyLayer and add a rule for acp_get_session_metrics: 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 Ambient Code Platform MCP Server. Nothing to install.
acp_get_session_metrics 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 acp_get_session_metrics 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 acp_get_session_metrics. 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.
acp_get_session_metrics is provided by the Ambient Code Platform MCP Server MCP server (jeremyeder/mcp). 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 →