AI agents call get_test_cycles to retrieve information from Mcp Jama without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns test cycle data without modifying, deleting, or executing any operations. It is a straightforward read operation consistent with other retrieval tools like 'get_item' and 'get_projects' on the same server. The blast radius of misuse is minimal—an AI agent could only access test cycle information that already exists.
From the tool's definition Tool name 'get_test_cycles' and description stating it 'retrieves a list of test cycles belonging to a test plan' (translated from Japanese) indicates data retrieval with no side effects.
Attacks that exploit this kind of access
テストプランに属するテストサイクル一覧を取得する. It is categorised as a Read tool in the Mcp Jama MCP Server, which means it retrieves data without modifying state.
Register the Mcp Jama MCP server in PolicyLayer and add a rule for get_test_cycles: 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 Mcp Jama. Nothing to install.
get_test_cycles 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_test_cycles 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_test_cycles. 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_test_cycles is provided by the Mcp Jama MCP server (keisukeshima/mcp-jama). 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 →