AI agents call testmo_list_issue_connections to retrieve information from Testmo without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name indicates a listing/retrieval operation on issue connections within Testmo. Despite the empty description, the semantic pattern of 'list_*' tools strongly suggests a Read operation that queries and returns data about existing issue connections without side effects. Confidence is reduced from 0.9 to 0.85 due to the missing description, but the naming convention is a reliable indicator.
From the tool's definition Tool name 'testmo_list_issue_connections' contains 'list', which retrieves or queries data without modification. The 'list' prefix is a standard pattern for Read operations that enumerate existing resources.
Attacks that exploit this kind of access
testmo_list_issue_connections. It is categorised as a Read tool in the Testmo MCP Server, which means it retrieves data without modifying state.
Register the Testmo MCP server in PolicyLayer and add a rule for testmo_list_issue_connections: 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 Testmo. Nothing to install.
testmo_list_issue_connections 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 testmo_list_issue_connections 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 testmo_list_issue_connections. 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.
testmo_list_issue_connections is provided by the Testmo MCP server (strelec00/testmo-mcp). 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 →