tag_search_results · Kontexta MCP: Risk & Policy

WHAT IT DOES

What tag_search_results does on Kontexta

AI agents use tag_search_results to create or update resources in Kontexta — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Kontexta environment.

WHY IT NEEDS A POLICY

Why tag_search_results needs a policy

The tool applies tags in bulk to search results, which is a write/modification operation on metadata. The description is truncated and uninformative beyond 'bulk-tag', lowering confidence slightly. Since tagging modifies data (adds tags) but is generally reversible, Write is the most appropriate category. Severity is medium given bulk operations can affect many records at once.

From the tool's definition Bulk-tag — run an FTS

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

tag_search_results Rate-limited

tag_search_results 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "tag_search_results": {
      "limits": [
        {
          "counter": "tag_search_results_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Kontexta, so you can run agents against it safely.

FAQ

Questions about tag_search_results

What does the tag_search_results tool do? +

Bulk-tag — run an FTS. It is categorised as a Write tool in the Kontexta MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on tag_search_results? +

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

What risk level is tag_search_results? +

tag_search_results is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit tag_search_results? +

Yes. Add a rate_limit block to the tag_search_results 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 tag_search_results completely? +

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

tag_search_results is provided by the Kontexta MCP server (safiyu/kontexta). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.