Extract ticket numbers from the current branch, commits, and optional additional text. Uses TICKET_PATTERN env var to find tickets in: 1. Branch name (e.g.,
AI agents call extract_tickets to retrieve information from Pr Narrator without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a query/retrieval operation that analyzes existing git metadata (branch name, commit messages, text) to extract information. It performs no side effects, creates no data irreversibly, executes no external commands, and moves no money. The parsing and extraction of ticket identifiers is purely informational, making it a Read category tool with low severity due to minimal blast radius from misuse.
From the tool's definition Tool 'extract_tickets' extracts/retrieves ticket numbers from branch names, commits, and text. Uses pattern matching to find and read existing ticket identifiers. No modification, deletion, execution, or financial action occurs.
Attacks that exploit this kind of access
Extract ticket numbers from the current branch, commits, and optional additional text. Uses TICKET_PATTERN env var to find tickets in: 1. Branch name (e.g.,. It is categorised as a Read tool in the Pr Narrator MCP Server, which means it retrieves data without modifying state.
Register the Pr Narrator MCP server in PolicyLayer and add a rule for extract_tickets: 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 Pr Narrator. Nothing to install.
extract_tickets 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 extract_tickets 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 extract_tickets. 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.
extract_tickets is provided by the Pr Narrator MCP server (mhaviv/pr-narrator-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 →