Low Risk

kit_get_tag

Get a specific tag

Part of the Kit MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

kit-mcp-server Read Risk 2/5

AI agents call kit_get_tag to retrieve information from Kit without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though kit_get_tag only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

io-github-aplaceforallmystuff-mcp-kit.yaml
tools:
  kit_get_tag:
    rules:
      - action: allow

See the full Kit policy for all 29 tools.

Tool Name kit_get_tag
Category Read
MCP Server Kit MCP Server
Risk Level Low

View all 29 tools →

Agents calling read-class tools like kit_get_tag have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

What does the kit_get_tag tool do? +

Get a specific tag. It is categorised as a Read tool in the Kit MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on kit_get_tag? +

Add a rule in your Intercept YAML policy under the tools section for kit_get_tag. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Kit MCP server.

What risk level is kit_get_tag? +

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

Can I rate-limit kit_get_tag? +

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

How do I block kit_get_tag completely? +

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

What MCP server provides kit_get_tag? +

kit_get_tag is provided by the Kit MCP server (kit-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Kit

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.