filename
Filename to update or create (string, required)
This record as markdown: /tools/io-github-aifity-omnigit-mcp/filename.md
What filename does on GitHub
AI agents use filename to create or update resources in GitHub, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your GitHub environment.
Why filename is rated Medium
This tool is a parameter that enables creation or modification of files reversibly. It does not delete data irreversibly. However, confidence is moderate (0.5) because the description is minimal and does not provide full context about the actual operation—it only describes what the parameter itself does rather than the tool's complete functionality.
From the tool's definition Tool named 'filename' with description 'Filename to update or create' suggests this parameter enables file creation or modification operations.
Attacks that exploit this kind of access
The rule that runs filename safely
PolicyLayer is an MCP gateway: it sits between your AI agents and GitHub, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For filename, this is the rule to start with:
filename 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.
The button opens the PolicyLayer dashboard: create your workspace, connect GitHub, apply this rule, and every filename call is checked against it from then on.
Questions about filename
Filename to update or create (string, required). It is categorised as a Write tool in the GitHub MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the GitHub MCP server in PolicyLayer and add a rule for filename: 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 GitHub. Nothing to install.
filename 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 filename 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 filename. 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.
filename is provided by the GitHub MCP server (oci:ghcr.io/aifity/omnigit-mcp:0.5.0). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on GitHub, and thousands of servers like it.
This server
Across the catalogue