query_playbook_execution_params

query_playbook_execution_params

Server SOAR MCP Server wuzhi-dev/soar-mcp
Category Read
Risk class Low
Parameters 00 required

What query_playbook_execution_params does on SOAR MCP Server

AI agents call query_playbook_execution_params 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.

Why query_playbook_execution_params needs a policy

This tool appears to retrieve parameters associated with playbook executions—a non-destructive read operation. While the empty description reduces confidence slightly, the 'query_' prefix and context among other query/list tools on the server suggest it retrieves execution metadata without side effects. Classified as Read with low severity due to the benign nature of accessing execution parameters.

From the tool's definition Tool name 'query_playbook_execution_params' contains 'query', indicating data retrieval. The description is empty, limiting direct evidence, but the naming convention and sibling tools (query_playbook_execution_result, query_playbook_execution_status)…

Questions about query_playbook_execution_params

What does the query_playbook_execution_params tool do? +

query_playbook_execution_params. It is categorised as a Read tool in the SOAR MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on query_playbook_execution_params? +

Register the SOAR MCP Server MCP server in PolicyLayer and add a rule for query_playbook_execution_params: 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.

What risk level is query_playbook_execution_params? +

query_playbook_execution_params is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit query_playbook_execution_params? +

Yes. Add a rate_limit block to the query_playbook_execution_params 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.

How do I block query_playbook_execution_params completely? +

Set action: deny in the PolicyLayer policy for query_playbook_execution_params. 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.

What MCP server provides query_playbook_execution_params? +

query_playbook_execution_params 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.

// THE FULL RECORD

query_playbook_execution_params is one line of SOAR MCP Server's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.