This record as markdown: /tools/github/create-gist.md
What create_gist does on GitHub
AI agents use create_gist to create or update resources in GitHub, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your GitHub environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
public | boolean | — | Whether the gist is public |
content | string | — | Content for simple single-file gist creation |
filename | string | — | Filename for simple single-file gist creation |
description | string | — | Description of the gist |
Parameters from the server's own tool schema.
Why create_gist is rated Medium
Creating a gist is a reversible write operation that generates new content on GitHub. It has medium severity because gists can be public, potentially exposing the AI's generated content to the internet, and could be used to leak sensitive information or create spam/malicious content. However, it is not destructive (gists can be deleted), not financial, and not an arbitrary code execution.
From the tool's definition Tool name is "create_gist" and description states "Create a new gist" — this creates new data in GitHub's gist service.
Risk signalsAccepts raw HTML/template content (content) · Accepts file system path (filename)
Attacks that exploit this kind of access
The rule that runs create_gist safely
PolicyLayer is an MCP gateway: it sits between your AI agents and GitHub, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_gist, this is the rule to start with:
create_gist 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 GitHub, apply this rule, and every create_gist call is checked against it from then on.
Questions about create_gist
Create a new gist. It is categorised as a Write tool in the GitHub MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
create_gist accepts 4 parameters: public, content, filename, description. The full parameter table on this page comes from the server's own tool schema.
Register the GitHub MCP server in PolicyLayer and add a rule for create_gist: 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 GitHub. Nothing to install.
create_gist 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 create_gist 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 create_gist. 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.
create_gist is provided by the GitHub MCP server (oci:ghcr.io/github/github-mcp-server:1.3.0). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on GitHub, and thousands of servers like it.
This server
Across the catalogue