add_dictionary_entry · Querywise MCP: Risk & Policy

WHAT IT DOES

What add_dictionary_entry does on Querywise

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

This tool creates or modifies entries in the data dictionary metadata store. While the description is empty (lowering confidence slightly), the name combined with the server's documented data dictionary feature and the presence of delete_* counterparts establishes this as a Write operation.

From the tool's definition Tool name 'add_dictionary_entry' indicates creation/modification of data (the data dictionary). Server context shows a semantic layer with a 'data dictionary' component alongside glossary and metrics.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_dictionary_entry Rate-limited

add_dictionary_entry 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_dictionary_entry": {
      "limits": [
        {
          "counter": "add_dictionary_entry_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_dictionary_entry

What does the add_dictionary_entry tool do? +

add_dictionary_entry. 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_dictionary_entry? +

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

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

Can I rate-limit add_dictionary_entry? +

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

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

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