✨ Create New Prompt: Create a new prompt and save it directly to the GitHub repository. 🎯 WORKFLOW: Always use search_prompts first to check if a similar prompt already exists. Only create new prompts when needed to avoid duplicates.
AI agents use create_github_prompt to create or update resources in Smart Prompts MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Smart Prompts MCP Server environment.
The tool creates and persists new data (prompts) to a GitHub repository. This is a Write operation because it creates/modifies data reversibly (new prompts can be subsequently edited or deleted via other tools on the server like delete_prompt). It does not execute arbitrary code, delete data irreversibly, or move money.
From the tool's definition Tool description explicitly states 'Create a new prompt and save it directly to the GitHub repository' — this is a create operation that modifies the repository state reversibly.
Documented attack patterns abuse exactly the kind of access create_github_prompt gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Smart Prompts MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for create_github_prompt:
{
"version": "1",
"default": "deny",
"tools": {
"create_github_prompt": {
"limits": [
{
"counter": "create_github_prompt_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_github_prompt 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.
Free to start. No card required.
✨ Create New Prompt: Create a new prompt and save it directly to the GitHub repository. 🎯 WORKFLOW: Always use search_prompts first to check if a similar prompt already exists. Only create new prompts when needed to avoid duplicates. It is categorised as a Write tool in the Smart Prompts MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Smart Prompts MCP Server MCP server in PolicyLayer and add a rule for create_github_prompt: 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 Smart Prompts MCP Server. Nothing to install.
create_github_prompt 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_github_prompt 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_github_prompt. 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_github_prompt is provided by the Smart Prompts MCP Server MCP server (jezweb/smart-prompts-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Smart Prompts MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
12 Smart Prompts MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.