Low Risk

get_github_issue

get_github_issue

How to control get_github_issue ↓

What get_github_issue does on Web Search MCP

AI agents call get_github_issue to retrieve information from Web Search MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_github_issue needs a policy

This tool retrieves GitHub issue information without modifying or deleting data. The lack of description reduces confidence slightly, but the naming convention and server's stated purpose (content extraction and search) strongly indicate read-only behavior. No side effects, code execution, financial, or destructive operations are implied.

From the tool's definition Tool name 'get_github_issue' and server context (Web Search MCP providing 'content extraction capabilities') indicate retrieval of GitHub issue data.

Documented attack patterns abuse exactly the kind of access get_github_issue gives an agent:

How to control get_github_issue

PolicyLayer is an MCP gateway — it sits between your AI agents and Web Search MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_github_issue:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_github_issue": {}
  }
}

get_github_issue is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Web Search MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_github_issue

What does the get_github_issue tool do? +

get_github_issue. It is categorised as a Read tool in the Web Search MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_github_issue? +

Register the Web Search MCP server in PolicyLayer and add a rule for get_github_issue: 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 Web Search MCP. Nothing to install.

What risk level is get_github_issue? +

get_github_issue is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_github_issue? +

Yes. Add a rate_limit block to the get_github_issue 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.

How do I block get_github_issue completely? +

Set action: deny in the PolicyLayer policy for get_github_issue. 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 get_github_issue? +

get_github_issue is provided by the Web Search MCP server (sydasif/web-search-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Web Search MCP tool call.

Start from Web Search MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

15 Web Search MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.