Fetch the status of a registered test group from QIT Manager.
AI agents call get_group_status to retrieve information from QIT 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 the current status of a test group from QIT Manager. The verb 'Fetch' and the read-only nature of status queries confirm this is a Read operation. There is no data modification, code execution, or irreversible action. The blast radius of misuse is minimal—an agent could only learn the status of test groups, which is informational data.
From the tool's definition Tool name 'get_group_status' and description 'Fetch the status of a registered test group' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
Fetch the status of a registered test group from QIT Manager. It is categorised as a Read tool in the QIT MCP Server MCP Server, which means it retrieves data without modifying state.
Register the QIT MCP Server MCP server in PolicyLayer and add a rule for get_group_status: 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 QIT MCP Server. Nothing to install.
get_group_status 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_group_status 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_group_status. 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_group_status is provided by the QIT MCP Server MCP server (woocommerce/qit-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 →