Get aggregated metrics and analytics from Langfuse.
AI agents call get_metrics to retrieve information from Langfuse Mcp Python without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and aggregates existing metrics and analytics data from Langfuse. It performs no modifications, deletions, executions, or financial operations. The read-only nature and absence of side effects classify it as a Read category tool with low severity, as misuse would only expose data visibility rather than cause operational damage.
From the tool's definition The tool is described as 'Get aggregated metrics and analytics from Langfuse,' which is purely a retrieval operation with the verb 'Get' indicating data querying without modification or side effects.
Attacks that exploit this kind of access
Get aggregated metrics and analytics from Langfuse. It is categorised as a Read tool in the Langfuse Mcp Python MCP Server, which means it retrieves data without modifying state.
Register the Langfuse Mcp Python MCP server in PolicyLayer and add a rule for get_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 Langfuse Mcp Python. Nothing to install.
get_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 get_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 get_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.
get_metrics is provided by the Langfuse Mcp Python MCP server (log-logn/langfuse-mcp-python). 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 →