Push multiple files to a GitHub repository in a single commit
Accepts file system path (files[].path); Accepts raw HTML/template content (files[].content); Single-target operation
Part of the Model Context Protocol Server for Smithery MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents use push_files to create or modify resources in Model Context Protocol Server for Smithery. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call push_files repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Model Context Protocol Server for Smithery.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
tools:
push_files:
rules:
- action: allow
rate_limit:
max: 30
window: 60See the full Model Context Protocol Server for Smithery policy for all 17 tools.
Agents calling write-class tools like push_files have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
Push multiple files to a GitHub repository in a single commit. It is categorised as a Write tool in the Model Context Protocol Server for Smithery MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Add a rule in your Intercept YAML policy under the tools section for push_files. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Model Context Protocol Server for Smithery MCP server.
push_files 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 push_files rule in your Intercept 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 Intercept policy for push_files. 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.
push_files is provided by the Model Context Protocol Server for Smithery MCP server (AlexKissiJr/unreal-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept