add_glossary_term · Querywise MCP: Risk & Policy

WHAT IT DOES

What add_glossary_term does on Querywise

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

WHY IT NEEDS A POLICY

Why add_glossary_term needs a policy

The 'add_' prefix indicates data creation/modification. Unlike destructive operations, glossary terms can be modified or removed (confirmed by sibling tool 'delete_glossary_term'). The operation is reversible and affects only metadata within the semantic layer, not production data.

From the tool's definition Tool name 'add_glossary_term' indicates creation of a new glossary entry. The description is empty, but the name and context (semantic layer management) clearly show this performs a reversible write operation creating metadata.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_glossary_term Rate-limited

add_glossary_term 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": {
    "add_glossary_term": {
      "limits": [
        {
          "counter": "add_glossary_term_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 Querywise, so you can run agents against it safely.

FAQ

Questions about add_glossary_term

What does the add_glossary_term tool do? +

add_glossary_term. It is categorised as a Write tool in the Querywise MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on add_glossary_term? +

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

What risk level is add_glossary_term? +

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

Can I rate-limit add_glossary_term? +

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

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

add_glossary_term is provided by the Querywise MCP server (kosminus/querywise-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.