git_tags

List tags.

SERVERYaver SOURCEyaver-cli

Low RISK CLASS

Category Read

Parameters 10 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-kivanccakmak-yaver/git-tags.md

WHAT IT DOES

What git_tags does on Yaver

AI agents call git_tags to retrieve information from Yaver without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameter	Type	Required	Description
`directory`	string	—

Parameters from the server's own tool schema.

RISK

Why git_tags is rated Low

This tool performs a simple read operation to list existing git tags. It has no side effects, does not execute code or commands, does not modify data, and does not delete anything. The blast radius of misuse is minimal—an agent could only retrieve tag information that is already publicly available in the repository.

From the tool's definition Tool name 'git_tags' with description 'List tags' indicates a query operation that retrieves git tag information without modifying, executing, or deleting anything.

Risk signalsAccepts file system path (directory)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs git_tags safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Yaver, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For git_tags, this is the rule to start with:

git_tags Allowed

git_tags is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "git_tags": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every git_tags call is checked against it from then on.

FAQ

Questions about git_tags

What does the git_tags tool do? +

List tags. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.

What parameters does git_tags accept? +

git_tags accepts 1 parameter: directory. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on git_tags? +

Register the Yaver MCP server in PolicyLayer and add a rule for git_tags: 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 Yaver. Nothing to install.

What risk level is git_tags? +

git_tags is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit git_tags? +

Yes. Add a rate_limit block to the git_tags 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.

How do I block git_tags completely? +

Set action: deny in the PolicyLayer policy for git_tags. 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.

What MCP server provides git_tags? +

git_tags is provided by the Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Yaver, and thousands of servers like it.

This server

All 645 Yaver tools →

Across the catalogue

get_cocktail_by_tags on Cocktails RAG MCP Server →claude_git_status on Claude Bridge → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →