Create a new pull request in a GitHub repository
AI agents use create_pull_request to create or update resources in Zerops Documentation MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Zerops Documentation MCP Server environment.
Creating a pull request is a write operation—it creates a new data object in GitHub that modifies the repository's state. While reversible (unlike destructive operations), it introduces artifacts that persist until manually removed.
From the tool's definition Tool name 'create_pull_request' and description 'Create a new pull request in a GitHub repository' indicate a write operation that modifies repository state by introducing a new PR object.
Attacks that exploit this kind of access
Create a new pull request in a GitHub repository. It is categorised as a Write tool in the Zerops Documentation MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Zerops Documentation MCP Server MCP server in PolicyLayer and add a rule for create_pull_request: 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 Zerops Documentation MCP Server. Nothing to install.
create_pull_request is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_pull_request 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 create_pull_request. 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.
create_pull_request is provided by the Zerops Documentation MCP Server MCP server (nermalcat69/zerops-mcp). 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 →