set_favorite · Kontexta MCP: Risk & Policy

WHAT IT DOES

What set_favorite does on Kontexta

AI agents use set_favorite 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 set_favorite needs a policy

This tool creates or modifies metadata (a favorite flag) in a local database. It is reversible and has no destructive, financial, or code-execution effects. It qualifies as Write because it changes persisted data state. Severity is low because the blast radius is minimal: toggling a favorite flag on a file has no cascading effects on system functionality, data integrity, or external systems.

From the tool's definition Tool description states it 'Set[s] or clear[s] the favorite flag on one file' and 'Persists to local SQLite', indicating modification of local state. The operation is explicitly idempotent and reversible—the user can change the flag back at any time.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

set_favorite Rate-limited

set_favorite 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": {
    "set_favorite": {
      "limits": [
        {
          "counter": "set_favorite_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 set_favorite

What does the set_favorite tool do? +

Set or clear the favorite flag on one file (idempotent — re-setting the same value is a no-op; not a toggle, you pass the desired state). Persists to local SQLite. No external auth or rate limits. Returns. 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 set_favorite? +

Register the Kontexta MCP server in PolicyLayer and add a rule for set_favorite: 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 set_favorite? +

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

Can I rate-limit set_favorite? +

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

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

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