create_demo_data · GitBranch MCP: Risk & Policy

WHAT IT DOES

What create_demo_data does on GitBranchMCP

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

WHY IT NEEDS A POLICY

Why create_demo_data needs a policy

This tool creates (generates/initializes) demo data rather than retrieving it, placing it in the Write category. The severity is medium because demo data creation is reversible and isolated to a demonstration context, with no financial impact or permanent system changes.

From the tool's definition Tool name 'create_demo_data' and description indicate it creates demonstration data. The description states it is called 'when users want to quickly demonstrate Free Mode capabilities or prepare portfolio showcases', which implies generating or initializing…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_demo_data Rate-limited

create_demo_data 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": {
    "create_demo_data": {
      "limits": [
        {
          "counter": "create_demo_data_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 GitBranchMCP, so you can run agents against it safely.

FAQ

Questions about create_demo_data

What does the create_demo_data tool do? +

当用户想快速演示 Free Mode 能力或准备作品集展示时调用。. It is categorised as a Write tool in the GitBranchMCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_demo_data? +

Register the GitBranch MCP server in PolicyLayer and add a rule for create_demo_data: 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 GitBranchMCP. Nothing to install.

What risk level is create_demo_data? +

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

Can I rate-limit create_demo_data? +

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

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

create_demo_data is provided by the GitBranch MCP server (lianggaoyuan/gitbranchmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.