当用户完成 demo 数据生成后，需要一次性导出演示 Markdown 文件时调用。
AI agents call export_demo_markdown to retrieve information from GitBranchMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool exports (reads/renders) demo data into a Markdown format. Export operations retrieve and format existing data without modifying or deleting it. The description says it is called when the user wants to export demo Markdown files at once after demo data generation. No write, execute, or destructive semantics are indicated. Severity is low because it only outputs demo/sample content.
From the tool's definition export_demo_markdown — exports a Markdown file from pre-generated demo data; sibling tools include 'export_branch_markdown' and 'export_main_markdown' which are clearly read/export operations
Attacks that exploit this kind of access
当用户完成 demo 数据生成后，需要一次性导出演示 Markdown 文件时调用。. It is categorised as a Read tool in the GitBranchMCP MCP Server, which means it retrieves data without modifying state.
Register the GitBranch MCP server in PolicyLayer and add a rule for export_demo_markdown: 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.
export_demo_markdown 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 export_demo_markdown 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 export_demo_markdown. 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.
export_demo_markdown 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.
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 →