list_github_mcp_tools

List available tools from GitHub MCP server (if enabled)

Server Chiro ERP - Issue Pipeline Orchestrator olwalgeorge2/mcp
Category Read
Risk class Low
Parameters 00 required

What list_github_mcp_tools does on Chiro ERP - Issue Pipeline Orchestrator

AI agents call list_github_mcp_tools to retrieve information from Chiro ERP - Issue Pipeline Orchestrator without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why list_github_mcp_tools needs a policy

This is a straightforward introspection tool that discovers what capabilities are available on an external MCP server. It performs no side effects, creates no data, executes no code, and deletes nothing. The blast radius of misuse is minimal—an agent could only learn what tools exist, which is low-risk information disclosure. Confidence is high because the description clearly indicates a read-only listing operation.

From the tool's definition Tool name 'list_github_mcp_tools' and description 'List available tools from GitHub MCP server (if enabled)' indicate a query/enumeration operation that retrieves metadata about available tools without modifying or executing anything.

Questions about list_github_mcp_tools

What does the list_github_mcp_tools tool do? +

List available tools from GitHub MCP server (if enabled). It is categorised as a Read tool in the Chiro ERP - Issue Pipeline Orchestrator MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_github_mcp_tools? +

Register the Chiro ERP - Issue Pipeline Orchestrator MCP server in PolicyLayer and add a rule for list_github_mcp_tools: 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 Chiro ERP - Issue Pipeline Orchestrator. Nothing to install.

What risk level is list_github_mcp_tools? +

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

Can I rate-limit list_github_mcp_tools? +

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

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

list_github_mcp_tools is provided by the Chiro ERP - Issue Pipeline Orchestrator MCP server (olwalgeorge2/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.