Initialize a git repository in the output directory. Creates .gitignore and initial commit.
AI agents use github_init to create or update resources in WP Astro MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your WP Astro MCP environment.
This tool performs Write-category operations: it creates files (.gitignore) and commits data to version control. While git operations are reversible (commits can be amended or reverted), the tool modifies the file system state persistently.
From the tool's definition The tool initializes a git repository, creates a .gitignore file, and makes an initial commit. These are file system writes that create and modify data (git metadata and configuration files) in a reversible manner.
Documented attack patterns abuse exactly the kind of access github_init gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and WP Astro MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for github_init:
{
"version": "1",
"default": "deny",
"tools": {
"github_init": {
"limits": [
{
"counter": "github_init_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}github_init 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.
Initialize a git repository in the output directory. Creates .gitignore and initial commit. It is categorised as a Write tool in the WP Astro MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the WP Astro MCP server in PolicyLayer and add a rule for github_init: 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 WP Astro MCP. Nothing to install.
github_init 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 github_init 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 github_init. 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.
github_init is provided by the WP Astro MCP server (vapvarun/wp-astro-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from WP Astro MCP, 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.
60 WP Astro MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.