Low Risk

check_github_status

Check GitHub connection status and write access. Use this to verify GitHub operations are available.

How to control check_github_status ↓

What check_github_status does on Smart Prompts MCP Server

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

Low Risk

Why check_github_status needs a policy

This tool performs a diagnostic query to verify GitHub API connectivity and permissions. While it queries whether write access is available, the tool itself performs no write, execute, or destructive operations—it merely reads and reports status.

From the tool's definition The tool description states it "Check[s] GitHub connection status and write access" — the operation is a status check/verification, which is a read-only query.

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

How to control check_github_status

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

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

check_github_status 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 Smart Prompts MCP Server — 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 check_github_status

What does the check_github_status tool do? +

Check GitHub connection status and write access. Use this to verify GitHub operations are available. It is categorised as a Read tool in the Smart Prompts MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on check_github_status? +

Register the Smart Prompts MCP Server MCP server in PolicyLayer and add a rule for check_github_status: 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 Smart Prompts MCP Server. Nothing to install.

What risk level is check_github_status? +

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

Can I rate-limit check_github_status? +

Yes. Add a rate_limit block to the check_github_status 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 check_github_status completely? +

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

check_github_status is provided by the Smart Prompts MCP Server MCP server (jezweb/smart-prompts-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Smart Prompts MCP Server tool call.

Start from Smart Prompts MCP Server, 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.

12 Smart Prompts MCP Server 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.