get_metric
AI agents call get_metric to retrieve information from Northbeam MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'get_metric' tool appears to retrieve marketing analytics data based on context from the server description and naming patterns of sibling tools. No modification, deletion, execution, or financial operations are indicated. The empty description limits confidence slightly, but the consistent naming pattern with other 'get_*' and 'list_*' tools strongly suggests read-only data retrieval with no side effects.
From the tool's definition Tool name 'get_metric' combined with sibling tools that include 'get_attribution', 'get_channel_performance', 'get_cohort_analysis', and 'list_metrics' indicate retrieval operations.
Attacks that exploit this kind of access
get_metric. It is categorised as a Read tool in the Northbeam MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Northbeam MCP Server MCP server in PolicyLayer and add a rule for get_metric: 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 Northbeam MCP Server. Nothing to install.
get_metric 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_metric 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_metric. 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_metric is provided by the Northbeam MCP Server MCP server (mattcoatsworth/northbeam-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 →