AI agents call get_plans to retrieve information from QASE MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves test plan data from a Qase project without creating, modifying, or deleting any resources. It is a read-only operation with minimal blast radius if misused—an AI agent could retrieve test plan information but cannot alter project state or cause harm.
From the tool's definition Tool name 'get_plans' and description 'Get all test plans in a project' indicate a retrieval operation with no mutation or side effects.
Documented attack patterns abuse exactly the kind of access get_plans gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and QASE MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_plans:
{
"version": "1",
"default": "deny",
"tools": {
"get_plans": {}
}
}get_plans 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 all test plans in a project. It is categorised as a Read tool in the QASE MCP Server MCP Server, which means it retrieves data without modifying state.
Register the QASE MCP Server MCP server in PolicyLayer and add a rule for get_plans: 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 QASE MCP Server. Nothing to install.
get_plans 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_plans 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_plans. 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_plans is provided by the QASE MCP Server MCP server (rikuson/mcp-qase). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from QASE MCP Server, 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.
26 QASE MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.