AI agents call get_shared_step 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 retrieves information about a specific shared step from the Qase test management platform. It performs a simple query/fetch operation with no side effects, no data modification, no code execution, and no destructive actions. This is a standard Read category tool with low severity as it only accesses existing data.
From the tool's definition Tool name 'get_shared_step' and description 'Get a specific shared step' clearly indicate a retrieval operation with no modification or deletion of data.
Documented attack patterns abuse exactly the kind of access get_shared_step 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_shared_step:
{
"version": "1",
"default": "deny",
"tools": {
"get_shared_step": {}
}
}get_shared_step 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 a specific shared step. 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_shared_step: 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_shared_step 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_shared_step 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_shared_step. 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_shared_step 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.