Release a dormant Kakao alimtalk template. SAFETY: requires confirmed=true.
AI agents use release_dormant_kakao_template to create or update resources in SOLAPI MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your SOLAPI MCP Server environment.
Releasing a dormant template reactivates it, which is a reversible state change (Write). It does not delete data, execute code, or involve financial transactions. The safety guard (confirmed=true) suggests some risk but the action is essentially a status update that can be re-dormanted.
From the tool's definition Release a dormant Kakao alimtalk template. SAFETY: requires confirmed=true.
Attacks that exploit this kind of access
Release a dormant Kakao alimtalk template. SAFETY: requires confirmed=true. It is categorised as a Write tool in the SOLAPI MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the SOLAPI MCP Server MCP server in PolicyLayer and add a rule for release_dormant_kakao_template: 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 SOLAPI MCP Server. Nothing to install.
release_dormant_kakao_template 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 release_dormant_kakao_template 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 release_dormant_kakao_template. 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.
release_dormant_kakao_template is provided by the SOLAPI MCP Server MCP server (solapi/solapi-mcp-server). 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 →