upsert_playbook_metadata

WHAT IT DOES

What upsert_playbook_metadata does on ReliaQuest GreyMatter MCP Server

AI agents use upsert_playbook_metadata to create or update resources in ReliaQuest GreyMatter MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ReliaQuest GreyMatter MCP Server environment.

WHY IT NEEDS A POLICY

Why upsert_playbook_metadata needs a policy

The 'upsert' operation is inherently a reversible write action that creates or updates data. Playbook metadata changes could affect incident response automation and workflows, but are not destructive (data can be reverted), financial, or arbitrary code execution. The mutation context confirms this is a data modification tool.

From the tool's definition Tool name uses 'upsert' (create or update operation) and is explicitly labeled as a mutation in the description. Mutations in GraphQL modify data, and playbook metadata management involves creating or updating configuration.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

upsert_playbook_metadata Rate-limited

upsert_playbook_metadata stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "upsert_playbook_metadata": {
      "limits": [
        {
          "counter": "upsert_playbook_metadata_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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 upsert_playbook_metadata

What does the upsert_playbook_metadata tool do? +

Playbooks \u00b7 mutation upsertPlaybookMetadata. Variables: input. Example variables: {\. It is categorised as a Write tool in the ReliaQuest GreyMatter MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on upsert_playbook_metadata? +

Register the ReliaQuest GreyMatter MCP Server MCP server in PolicyLayer and add a rule for upsert_playbook_metadata: 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 upsert_playbook_metadata? +

upsert_playbook_metadata is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit upsert_playbook_metadata? +

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

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

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