agent_metrics

Get performance metrics for agents (V2 compatible). Deprecated: Use agent/status with includeMetrics instead.

SERVERHamza Agent Hub 252 SOURCEhamzachallenge3-dev/hamza-agent-hub-252

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/hamza-agent-hub-252/agent-metrics.md

WHAT IT DOES

What agent_metrics does on Hamza Agent Hub 252

AI agents call agent_metrics to retrieve information from Hamza Agent Hub 252 without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why agent_metrics is rated Low

This tool queries and retrieves performance metrics from existing agents without modifying, executing, or deleting any data. It is purely observational, making it a Read operation with low severity risk.

From the tool's definition Tool name 'agent_metrics' and description 'Get performance metrics for agents' indicates a retrieval operation with no side effects. Explicitly stated as deprecated in favor of agent/status with includeMetrics, confirming read-only nature.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs agent_metrics safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Hamza Agent Hub 252, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For agent_metrics, this is the rule to start with:

agent_metrics Allowed

agent_metrics is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "agent_metrics": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Hamza Agent Hub 252, apply this rule, and every agent_metrics call is checked against it from then on.

FAQ

Questions about agent_metrics

What does the agent_metrics tool do? +

Get performance metrics for agents (V2 compatible). Deprecated: Use agent/status with includeMetrics instead. It is categorised as a Read tool in the Hamza Agent Hub 252 MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on agent_metrics? +

Register the Hamza Agent Hub 252 MCP server in PolicyLayer and add a rule for agent_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 Hamza Agent Hub 252. Nothing to install.

What risk level is agent_metrics? +

agent_metrics is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit agent_metrics? +

Yes. Add a rate_limit block to the agent_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.

How do I block agent_metrics completely? +

Set action: deny in the PolicyLayer policy for agent_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.

What MCP server provides agent_metrics? +

agent_metrics is provided by the Hamza Agent Hub 252 MCP server (hamzachallenge3-dev/hamza-agent-hub-252). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Hamza Agent Hub 252, and thousands of servers like it.

This server

All 581 Hamza Agent Hub 252 tools →

Across the catalogue

get_customer_metrics on 08-AI-Business-Agent →comfy_agent_compute on Comfy → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →