addScreen · Verblaze MCP Server MCP: Risk & Policy

WHAT IT DOES

What addScreen does on Verblaze MCP Server

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

WHY IT NEEDS A POLICY

Why addScreen needs a policy

The tool creates new translatable screens/files in a localization project. This is a Write operation because it adds data to the system reversibly. Severity is medium rather than high because the blast radius is limited to a single localization project's structure, and the action is not destructive or irreversible. Confidence is high because the intent is clear from both the name and description.

From the tool's definition Tool name 'addScreen' and description 'Add a new screen/file to all languages in a Verblaze project' indicate creation of new resources across the project. This is a reversible modification (screens can be removed via sibling 'removeScreen' tool).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

addScreen Rate-limited

addScreen 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": {
    "addScreen": {
      "limits": [
        {
          "counter": "addscreen_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 Verblaze MCP Server, so you can run agents against it safely.

FAQ

Questions about addScreen

What does the addScreen tool do? +

Add a new screen/file to all languages in a Verblaze project. REQUIRED: fileKey OR fileTitle. If only fileTitle is provided, fileKey will be generated automatically. Example: { fileKey:. It is categorised as a Write tool in the Verblaze MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on addScreen? +

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

What risk level is addScreen? +

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

Can I rate-limit addScreen? +

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

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

addScreen is provided by the Verblaze MCP Server MCP server (verblaze/verblaze_mcp_server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.