Get a list of tags used in Qiita.
AI agents call get_tags to retrieve information from Qiita 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 and queries data about tags without any side effects, modifications, or external operations. It fits the Read category definition of retrieving or querying data with no side effects. The severity is low because exposing a list of available tags poses minimal security risk—this is typically public metadata with no sensitive information exposure or misuse potential.
From the tool's definition Tool name 'get_tags' and description 'Get a list of tags used in Qiita' indicate data retrieval with no modification capability. This is a pure query operation that returns metadata about available tags.
Attacks that exploit this kind of access
Get a list of tags used in Qiita. It is categorised as a Read tool in the Qiita MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Qiita MCP Server MCP server in PolicyLayer and add a rule for get_tags: 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 MCP Server. Nothing to install.
get_tags 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 get_tags 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 get_tags. 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.
get_tags is provided by the Qiita MCP Server MCP server (ningen/qiita-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 →