AI agents call list_test_results to retrieve information from Agent Bus without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves and presents recorded test results, build logs, and lint evidence. It has no side effects, cannot execute code, and cannot modify data. The action is purely informational/observational, fitting the Read category. Severity is low because misuse only affects what information is accessed, not system state or external operations.
From the tool's definition Tool name contains 'list' (data retrieval) and description states 'List recorded test/build/lint evidence' — a query operation that retrieves historical test results without modifying or executing anything.
Attacks that exploit this kind of access
List recorded test/build/lint evidence. It is categorised as a Read tool in the Agent Bus MCP Server, which means it retrieves data without modifying state.
Register the Agent Bus MCP server in PolicyLayer and add a rule for list_test_results: 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 Agent Bus. Nothing to install.
list_test_results 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 list_test_results 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 list_test_results. 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.
list_test_results is provided by the Agent Bus MCP server (mustaphasteph/agent-bus). 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 →