pr-view
Views a pull request by number, URL, or branch. Returns structured data with state, checks, review decision, diff stats, author, labels, draft status, assignees, milestone, and timestamps.
This record as markdown: /tools/io-github-dave-london-http/pr-view.md
What pr-view does on Http
AI agents call pr-view to retrieve information from Http without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why pr-view is rated Low
This tool queries and retrieves information about pull requests without modifying data, executing code, or triggering side effects. It is a straightforward read operation with minimal risk. The only potential concern would be if the retrieved data contains sensitive information, but that is a data sensitivity issue rather than a tool capability risk.
From the tool's definition Tool description states it 'Views a pull request' and 'Returns structured data' — purely a retrieval operation with no modification, deletion, or execution of external commands.
Attacks that exploit this kind of access
The rule that runs pr-view safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Http, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For pr-view, this is the rule to start with:
pr-view is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Http, apply this rule, and every pr-view call is checked against it from then on.
Questions about pr-view
Views a pull request by number, URL, or branch. Returns structured data with state, checks, review decision, diff stats, author, labels, draft status, assignees, milestone, and timestamps. It is categorised as a Read tool in the Http MCP Server, which means it retrieves data without modifying state.
Register the Http MCP server in PolicyLayer and add a rule for pr-view: 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 Http. Nothing to install.
pr-view 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 pr-view 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 pr-view. 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.
pr-view is provided by the Http MCP server (@paretools/http). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Http, and thousands of servers like it.
This server
Across the catalogue