open_pull_request
Turn a ticket
This record as markdown: /tools/ai-featureboard-featureboard/open-pull-request.md
What open_pull_request does on FeatureBoard
AI agents use open_pull_request to create or update resources in FeatureBoard, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your FeatureBoard environment.
Why open_pull_request is rated Medium
Opening a pull request creates a new, reversible entity in a repository. This is a Write operation (creates data) rather than Execute (which would require running arbitrary code) or Destructive (PRs can be closed/reverted). The incomplete description lowers confidence slightly, but the tool name and server context (project board for shipping tickets) support Write classification.
From the tool's definition Tool name 'open_pull_request' indicates creation of a pull request. Description 'Turn a ticket' is incomplete but contextually suggests converting/transforming a ticket into a PR, which creates a new entity in version control.
Attacks that exploit this kind of access
The rule that runs open_pull_request safely
PolicyLayer is an MCP gateway: it sits between your AI agents and FeatureBoard, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For open_pull_request, this is the rule to start with:
open_pull_request 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.
The button opens the PolicyLayer dashboard: create your workspace, connect FeatureBoard, apply this rule, and every open_pull_request call is checked against it from then on.
Questions about open_pull_request
Turn a ticket. It is categorised as a Write tool in the FeatureBoard MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the FeatureBoard MCP server in PolicyLayer and add a rule for open_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 FeatureBoard. Nothing to install.
open_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 open_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 open_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.
open_pull_request is provided by the FeatureBoard MCP server (https://github.com/valentil/featureboard-mcp/releases/download/v0.7/featureboard.plugin). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on FeatureBoard, and thousands of servers like it.
This server
Across the catalogue