info

Runs

SERVERGo SOURCEDave-London/Pare

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-dave-london-go/info.md

WHAT IT DOES

What info does on Go

AI agents invoke info to trigger actions in Go. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

RISK

Why info is rated High

The description is cut off at 'Runs', strongly implying execution of some Go-related command or tool. Given the server context of structured Go tool output (build, test, vet), this tool likely executes a Go informational command (e.g., 'go info' or similar). Classified as Execute due to running an external process, with medium severity since informational commands typically have limited blast radius.

From the tool's definition Tool name is 'info' and description is truncated/uninformative ('Runs' only). Server context involves Go tooling (build, test, vet).

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs info safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Go, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For info, this is the rule to start with:

info Rate-limited

info stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "info": {
      "limits": [
        {
          "counter": "info_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Go, apply this rule, and every info call is checked against it from then on.

FAQ

Questions about info

What does the info tool do? +

Runs. It is categorised as a Execute tool in the Go MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on info? +

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

What risk level is info? +

info is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit info? +

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

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

info is provided by the Go MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Go, and thousands of servers like it.

This server

All 202 Go tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →