Deploy app settings to production
AI agents invoke deployApp to trigger actions in kintone OAuth MCP Server on Cloudflare Workers. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes a deployment action that modifies the live production state of a kintone app. While not technically destructive (settings can be reverted), it is an Execute-class tool because it triggers an external operation whose consequences depend on what settings are being deployed. The high severity reflects the blast radius: a misconfigured or malicious deployment could disrupt service for all app users.
From the tool's definition The tool performs 'Deploy app settings to production', which triggers an external operation (deployment) with irreversible side effects in a production environment.
Attacks that exploit this kind of access
Deploy app settings to production. It is categorised as a Execute tool in the kintone OAuth MCP Server on Cloudflare Workers MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the kintone OAuth MCP Server on Cloudflare Workers MCP server in PolicyLayer and add a rule for deployApp: 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 OAuth MCP Server on Cloudflare Workers. Nothing to install.
deployApp is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the deployApp 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 deployApp. 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.
deployApp is provided by the kintone OAuth MCP Server on Cloudflare Workers MCP server (r3-yamauchi/kintone-oauth-mcp-server-cfw). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →