AI agents invoke gwanjong_strike to trigger actions in Gwanjong. 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 social media operations (posting comments, creating posts, upvoting content) that have real-world effects on external platforms. While not destructive (posts can be deleted) or financial, it clearly performs Execute-category actions: triggering external operations whose consequences depend on the arguments provided.
From the tool's definition Description explicitly states 'Execute: comment, post, or upvote' — these are actions that trigger external operations on social media platforms (Dev.to, Bluesky, Twitter, Reddit).
Attacks that exploit this kind of access
Execute: comment, post, or upvote. Uses context cached from draft. It is categorised as a Execute tool in the Gwanjong MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Gwanjong MCP server in PolicyLayer and add a rule for gwanjong_strike: 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 Gwanjong. Nothing to install.
gwanjong_strike 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 gwanjong_strike 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 gwanjong_strike. 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.
gwanjong_strike is provided by the Gwanjong MCP server (sonaiengine/gwanjong-mcp). 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 →