This record as markdown: /tools/io-github-dave-london-build/info.md
What info does on Build
AI agents invoke info to trigger actions in Build. 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.
Why info is rated High
Given the server context (build tool that runs tsc, generic commands, ansible, bazel, etc.) and the partial description 'Runs', this tool likely executes some kind of informational command or query. Since the description is incomplete, confidence is low. The most likely interpretation based on the server's purpose and sibling tools is that it executes a command to retrieve build/environment information.
From the tool's definition Tool name is 'info' on a build server described as running structured build tool output (tsc, generic commands). The description appears to be truncated ('Runs' with no further detail).
Attacks that exploit this kind of access
The rule that runs info safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Build, 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 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Build, apply this rule, and every info call is checked against it from then on.
Questions about info
Runs. It is categorised as a Execute tool in the Build MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Build 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 Build. Nothing to install.
info is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
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.
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.
info is provided by the Build MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Build, and thousands of servers like it.
Across the catalogue