AI agents use move_app_to_space 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.
This tool modifies the state of Kintone by changing an app's location/space association. It is reversible (the app can be moved back), so it qualifies as Write rather than Destructive. The severity is medium because moving an app could affect access controls and visibility for users, potentially disrupting workflows, but doesn't delete data or trigger financial transactions.
From the tool's definition Tool name 'move_app_to_space' and description 'kintoneアプリを指定したスペースに移動します' (move Kintone app to specified space) indicate modifying organizational structure by relocating an app. This is a reversible modification operation.
Documented attack patterns abuse exactly the kind of access move_app_to_space gives an agent:
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 move_app_to_space:
{
"version": "1",
"default": "deny",
"tools": {
"move_app_to_space": {
"limits": [
{
"counter": "move_app_to_space_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}move_app_to_space 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.
Free to start. No card required.
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.
Register the Kintone MCP Server MCP server in PolicyLayer and add a rule for move_app_to_space: 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.
move_app_to_space is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the move_app_to_space 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.
Set action: deny in the PolicyLayer policy for move_app_to_space. 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.
move_app_to_space 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.
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.