update_tile · Slite MCP Server MCP: Risk & Policy

WHAT IT DOES

What update_tile does on Slite MCP Server

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

WHY IT NEEDS A POLICY

Why update_tile needs a policy

The tool creates or modifies data reversibly—tiles can be edited or removed later. It does not delete data irreversibly (Destructive), execute arbitrary code (Execute), move money (Financial), or merely read data (Read). The severity is medium because unintended tile modifications could corrupt note content or introduce misinformation into the knowledge base, but changes are reversible.

From the tool's definition Tool name 'update_tile' and description 'Update or create a tile in a Slite note' indicate the tool modifies (or creates) content within notes.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_tile Rate-limited

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

FAQ

Questions about update_tile

What does the update_tile tool do? +

Update or create a tile in a Slite note. It is categorised as a Write tool in the Slite 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 update_tile? +

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

What risk level is update_tile? +

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

Can I rate-limit update_tile? +

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

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

update_tile is provided by the Slite MCP Server MCP server (takeokunn/slite-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.