Push multiple files to a GitHub repository in a single commit
Risk signalsAccepts file system path (files[].path) · Accepts raw HTML/template content (files[].content)
Part of the Andy's Test API MCP Server server.
Free to start. No card required.
AI agents use push_files to create or modify resources in Andy's Test API MCP Server. 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. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Andy's Test API MCP Server.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"push_files": {
"limits": [
{
"counter": "push_files_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full Andy's Test API MCP Server policy for all 17 tools.
These attack patterns abuse exactly the kind of access push_files gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Push multiple files to a GitHub repository in a single commit. It is categorised as a Write tool in the Andy's Test API MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Andy's Test API MCP Server MCP server in PolicyLayer and add a rule for push_files: 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 Andy's Test API MCP Server. Nothing to install.
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 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 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 Andy's Test API MCP Server MCP server (AndyManastorm/smithery-reference-servers). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 17 Andy's Test API MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.