Medium Risk

update_views

kintoneアプリの一覧(ビュー)の設定を更新します

How to control update_views ↓

What update_views does on Kintone MCP Server

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

Medium Risk

Why update_views needs a policy

This tool updates view configurations (一覧(ビュー)の設定) for Kintone apps, which is a reversible modification operation. It does not execute arbitrary code, delete data irreversibly, or move money, making it Write rather than Execute, Destructive, or Financial.

From the tool's definition Tool name is 'update_views' and description states '更新します' (update/modify), indicating modification of Kintone app view configurations.

Documented attack patterns abuse exactly the kind of access update_views gives an agent:

How to control update_views

PolicyLayer is an MCP gateway — it sits between your AI agents and Kintone MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for update_views:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_views": {
      "limits": [
        {
          "counter": "update_views_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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

  1. Create a free account and register Kintone MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about update_views

What does the update_views tool do? +

kintoneアプリの一覧(ビュー)の設定を更新します. It is categorised as a Write tool in the Kintone 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_views? +

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

What risk level is update_views? +

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

Can I rate-limit update_views? +

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

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

update_views is provided by the Kintone MCP Server MCP server (r3-yamauchi/kintone-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Kintone MCP Server tool call.

Start from Kintone MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

70 Kintone MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.