gist-create
Creates a new GitHub gist from one or more files. Returns structured data with gist ID, URL, visibility, file names, description, and file count.
This record as markdown: /tools/io-github-dave-london-build/gist-create.md
What gist-create does on Build
AI agents use gist-create to create or update resources in Build, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Build environment.
Why gist-create is rated Medium
This tool creates new resources (GitHub gists) on a remote service, which is a reversible write operation. While it doesn't execute arbitrary code or delete data, an AI agent misusing this could spam gists, leak sensitive information, or create unwanted public content. Severity is medium because gists can be deleted/made private (reversible) and the blast radius is limited to GitHub gist creation.
From the tool's definition Tool name 'gist-create' and description states it 'Creates a new GitHub gist from one or more files.' The verb 'creates' and the function of posting new content to GitHub indicates a write operation that modifies state on an external service.
Attacks that exploit this kind of access
The rule that runs gist-create 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 gist-create, this is the rule to start with:
gist-create stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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 gist-create call is checked against it from then on.
Questions about gist-create
Creates a new GitHub gist from one or more files. Returns structured data with gist ID, URL, visibility, file names, description, and file count. It is categorised as a Write tool in the Build MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Build MCP server in PolicyLayer and add a rule for gist-create: 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.
gist-create is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the gist-create 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 gist-create. 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.
gist-create 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.
This server
Across the catalogue