Create a new local development environment from a GitHub repository
AI agents use local_dev_from_github to create or update resources in Mcp Local Dev — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Local Dev environment.
An AI agent can call local_dev_from_github faster than any human can review — one bad instruction and it creates or modifies resources in Mcp Local Dev by the hundred, each call as confident as the last.
Documented attack patterns abuse exactly the kind of access local_dev_from_github gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Local Dev, and nothing reaches the server without passing your rules. This is the rule we recommend for local_dev_from_github:
{
"version": "1",
"default": "deny",
"tools": {
"local_dev_from_github": {
"limits": [
{
"counter": "local_dev_from_github_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}local_dev_from_github 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 a new local development environment from a GitHub repository. It is categorised as a Write tool in the Mcp Local Dev MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Local Dev MCP server in PolicyLayer and add a rule for local_dev_from_github: 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 Mcp Local Dev. Nothing to install.
local_dev_from_github 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 local_dev_from_github 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 local_dev_from_github. 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.
local_dev_from_github is provided by the Mcp Local Dev MCP server (txbm/mcp-local-dev). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 4 Mcp Local Dev tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4 Mcp Local Dev tools catalogued and risk-classified — across an index of 42,500+ MCP servers.