指定されたタグをフォローしているかどうかを確認します
AI agents call is_tag_followed to retrieve information from Qiita API MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves user follow status for a tag, returning a boolean or similar state information. It is a pure read operation that queries existing data without creating, modifying, deleting, or executing anything. The low severity reflects minimal blast radius—misuse would only return incorrect follow status information, not enable destructive or financial actions.
From the tool's definition Tool name 'is_tag_followed' and description '指定されたタグをフォローしているかどうかを確認します' (Check whether a specified tag is being followed) indicate a query/status check operation with no data modification or side effects.
Attacks that exploit this kind of access
指定されたタグをフォローしているかどうかを確認します. It is categorised as a Read tool in the Qiita API MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Qiita API MCP Server MCP server in PolicyLayer and add a rule for is_tag_followed: 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.
is_tag_followed is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the is_tag_followed 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 is_tag_followed. 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.
is_tag_followed 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 →