Crea un tag en un repositorio (sin release)
AI agents use create_tag to create or update resources in Mcp Github — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Github environment.
Creating a tag modifies the repository by adding a new reference/pointer to a commit. This is a reversible write operation (tags can be deleted), not destructive. It does not execute arbitrary code, move money, or read data. The severity is medium because misuse could clutter the repository or interfere with release workflows, but the impact is limited in scope and reversible.
From the tool's definition Tool name 'create_tag' and description 'Crea un tag en un repositorio (sin release)' indicate creation of a Git tag object, which creates/modifies repository metadata.
Attacks that exploit this kind of access
Crea un tag en un repositorio (sin release). It is categorised as a Write tool in the Mcp Github MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Github MCP server in PolicyLayer and add a rule for create_tag: 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 Github. Nothing to install.
create_tag 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 create_tag 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 create_tag. 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.
create_tag is provided by the Mcp Github MCP server (pblarismendi/mcp-github-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →