Exibe as métricas de evolução do sistema Multi-Agent.
AI agents call get_system_metrics to retrieve information from GPA Backend Test Analyst MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays system metrics—a read-only operation with no side effects, no code execution, no data modification, and no destructive actions. It falls squarely into the Read category. Severity is low because metrics retrieval poses minimal risk; misuse would only expose performance data, not enable harmful actions.
From the tool's definition Tool name 'get_system_metrics' and description 'Exibe as métricas de evolução do sistema Multi-Agent' (Portuguese: 'Displays the metrics of evolution of the Multi-Agent system') indicate retrieval of performance/evolution metrics without modification or…
Attacks that exploit this kind of access
Exibe as métricas de evolução do sistema Multi-Agent. It is categorised as a Read tool in the GPA Backend Test Analyst MCP MCP Server, which means it retrieves data without modifying state.
Register the GPA Backend Test Analyst MCP server in PolicyLayer and add a rule for get_system_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 GPA Backend Test Analyst MCP. Nothing to install.
get_system_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_system_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_system_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_system_metrics is provided by the GPA Backend Test Analyst MCP server (renanpires-tech/mcpautomation). 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 →