Medium Risk

issue-view

Views an issue by number or URL. Returns structured data with state, labels, assignees, author, milestone, close reason, and body.

Accepts file system path (path)

Part of the Github MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

@paretools/github Write Risk 3/5

AI agents use issue-view to create or modify resources in Github. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call issue-view repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Github.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

io-github-dave-london-github.yaml
tools:
  issue-view:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full Github policy for all 27 tools.

Tool Name issue-view
Category Write
MCP Server Github MCP Server
Risk Level Medium

View all 27 tools →

Agents calling write-class tools like issue-view have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

What does the issue-view tool do? +

Views an issue by number or URL. Returns structured data with state, labels, assignees, author, milestone, close reason, and body.. It is categorised as a Write tool in the Github MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on issue-view? +

Add a rule in your Intercept YAML policy under the tools section for issue-view. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Github MCP server.

What risk level is issue-view? +

issue-view is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit issue-view? +

Yes. Add a rate_limit block to the issue-view rule in your Intercept 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.

How do I block issue-view completely? +

Set action: deny in the Intercept policy for issue-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.

What MCP server provides issue-view? +

issue-view is provided by the Github MCP server (@paretools/github). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Github

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.