rerun_all_failed_tasks_for_playbook_run

WHAT IT DOES

What rerun_all_failed_tasks_for_playbook_run does on ReliaQuest GreyMatter MCP Server

AI agents invoke rerun_all_failed_tasks_for_playbook_run to trigger actions in ReliaQuest GreyMatter MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why rerun_all_failed_tasks_for_playbook_run needs a policy

This tool executes external operations (task re-execution) whose side effects depend on the playbook's logic and configuration. It is not merely retrieving data (Read), nor is it safely reversible (Write). The blast radius includes unintended task execution, potential state changes, or repeated actions if a playbook contains destructive operations.

From the tool's definition Tool name 'rerun_all_failed_tasks_for_playbook_run' indicates execution of previously failed tasks within a playbook run.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

rerun_all_failed_tasks_for_playbook_run Rate-limited

rerun_all_failed_tasks_for_playbook_run stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "rerun_all_failed_tasks_for_playbook_run": {
      "limits": [
        {
          "counter": "rerun_all_failed_tasks_for_playbook_run_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches ReliaQuest GreyMatter MCP Server, so you can run agents against it safely.

FAQ

Questions about rerun_all_failed_tasks_for_playbook_run

What does the rerun_all_failed_tasks_for_playbook_run tool do? +

Playbooks \u00b7 mutation rerunAllFailedTasksForPlaybookRun. Variables: playbookRunId. Example variables: {\. It is categorised as a Execute tool in the ReliaQuest GreyMatter MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on rerun_all_failed_tasks_for_playbook_run? +

Register the ReliaQuest GreyMatter MCP Server MCP server in PolicyLayer and add a rule for rerun_all_failed_tasks_for_playbook_run: 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 ReliaQuest GreyMatter MCP Server. Nothing to install.

What risk level is rerun_all_failed_tasks_for_playbook_run? +

rerun_all_failed_tasks_for_playbook_run is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit rerun_all_failed_tasks_for_playbook_run? +

Yes. Add a rate_limit block to the rerun_all_failed_tasks_for_playbook_run 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 rerun_all_failed_tasks_for_playbook_run completely? +

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

rerun_all_failed_tasks_for_playbook_run is provided by the ReliaQuest GreyMatter MCP Server MCP server (space-c0wboy/reliaquest-greymatter-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.