指定されたユーザーのフォローを解除します
AI agents use unfollow_user to create or update resources in Qiita API MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Qiita API MCP Server environment.
Unfollowing a user removes a social relationship on the platform. This is a reversible write operation — the user can be re-followed at any time — so it does not qualify as Destructive. It has minimal blast radius as it only affects a social connection, not content or data.
From the tool's definition unfollow_user / 指定されたユーザーのフォローを解除します (unfollow the specified user)
Attacks that exploit this kind of access
指定されたユーザーのフォローを解除します. It is categorised as a Write tool in the Qiita API MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Qiita API MCP Server MCP server in PolicyLayer and add a rule for unfollow_user: 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 Qiita API MCP Server. Nothing to install.
unfollow_user 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 unfollow_user 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 unfollow_user. 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.
unfollow_user is provided by the Qiita API MCP Server MCP server (selenium39/mcp-server-qiita). 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 →