Low Risk

get_process_management

kintoneアプリのプロセス管理設定を取得します

How to control get_process_management ↓

What get_process_management does on Kintone MCP Server

AI agents call get_process_management to retrieve information from Kintone MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_process_management needs a policy

This tool retrieves configuration data about process management settings in a Kintone application. The 'get' prefix and 'retrieve' semantic (取得 = to get/retrieve) confirm this is a read-only operation that queries existing data without side effects. No data is created, modified, deleted, or any external operations are triggered.

From the tool's definition Tool name 'get_process_management' and description 'kintoneアプリのプロセス管理設定を取得します' (retrieves process management settings for a Kintone app) indicates a GET/retrieve operation with no modification capability.

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

How to control get_process_management

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 get_process_management:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_process_management": {}
  }
}

get_process_management is read-only, so it stays allowed — but 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.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_process_management

What does the get_process_management tool do? +

kintoneアプリのプロセス管理設定を取得します. It is categorised as a Read tool in the Kintone MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_process_management? +

Register the Kintone MCP Server MCP server in PolicyLayer and add a rule for get_process_management: 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 get_process_management? +

get_process_management is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_process_management? +

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

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

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