查询剧本执行状态 - 根据活动ID查询剧本执行状态
AI agents call query_playbook_execution_status to retrieve information from SOAR 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 the execution status of a security playbook based on an activity ID. It performs a read-only lookup operation without creating, modifying, deleting, or executing any actions. Even in a SOAR platform context where other tools execute playbooks, this specific tool is purely informational and poses minimal risk as it only returns status information.
From the tool's definition Tool name includes 'query' and description states '查询剧本执行状态' (query playbook execution status). The function retrieves execution status based on activity ID with no modification or side effects.
Attacks that exploit this kind of access
查询剧本执行状态 - 根据活动ID查询剧本执行状态. It is categorised as a Read tool in the SOAR MCP Server MCP Server, which means it retrieves data without modifying state.
Register the SOAR MCP Server MCP server in PolicyLayer and add a rule for query_playbook_execution_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 SOAR MCP Server. Nothing to install.
query_playbook_execution_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 query_playbook_execution_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 query_playbook_execution_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.
query_playbook_execution_status is provided by the SOAR MCP Server MCP server (wuzhi-dev/soar-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 →