AI agents use gwanjong_campaign to create or update resources in Gwanjong — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Gwanjong environment.
The 'create' and 'update' actions indicate the tool modifies campaign data reversibly, placing it in the Write category. However, severity is elevated to 'high' rather than 'medium' because campaigns drive coordinated social media posting across multiple platforms—misuse could result in spam, impersonation, or coordinated inauthentic behavior affecting real communities.
From the tool's definition Tool description explicitly lists actions including 'create', 'update', and 'report' on campaigns. The server context describes a 'scout-draft-strike pipeline' for social media engagement across Dev.to, Bluesky, Twitter, and Reddit.
Attacks that exploit this kind of access
Campaign management. action: create, list, get, update, report. It is categorised as a Write tool in the Gwanjong MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Gwanjong MCP server in PolicyLayer and add a rule for gwanjong_campaign: 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_campaign 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 gwanjong_campaign 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_campaign. 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_campaign 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 →