Get performance and power metrics for a specific build. Same metric types as get_app_perf_metrics but scoped to a single build. Useful for comparing performance between builds.
AI agents call get_build_perf_metrics to retrieve information from Asc without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves pre-computed performance and power metrics for builds. It performs a query/fetch operation that returns existing data without any side effects, reversible modifications, code execution, or financial impact. The low severity reflects minimal blast radius - misuse would only result in unauthorized access to performance telemetry data.
From the tool's definition Tool description states 'Get performance and power metrics for a specific build' - uses 'Get' verb indicating retrieval operation with no modification or execution of code.
Documented attack patterns abuse exactly the kind of access get_build_perf_metrics gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Asc, and nothing reaches the server without passing your rules. This is the rule we recommend for get_build_perf_metrics:
{
"version": "1",
"default": "deny",
"tools": {
"get_build_perf_metrics": {}
}
}get_build_perf_metrics is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get performance and power metrics for a specific build. Same metric types as get_app_perf_metrics but scoped to a single build. Useful for comparing performance between builds. It is categorised as a Read tool in the Asc MCP Server, which means it retrieves data without modifying state.
Register the Asc MCP server in PolicyLayer and add a rule for get_build_perf_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 Asc. Nothing to install.
get_build_perf_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_build_perf_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_build_perf_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_build_perf_metrics is provided by the Asc MCP server (asc-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Asc, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
14 Asc tools catalogued and risk-classified — across an index of 43,000+ MCP servers.