指定されたタグの記事一覧を取得します
AI agents call get_tag_items 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 or queries data (articles associated with a tag) without modifying, deleting, executing code, or creating financial obligations. It is a straightforward read operation typical of search or list functionality, presenting minimal risk of misuse even if invoked by an agent.
From the tool's definition Tool name 'get_tag_items' and description stating '指定されたタグの記事一覧を取得します' (retrieves a list of articles for the specified tag) indicate a query/retrieval operation with no 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 get_tag_items: 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.
get_tag_items 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_tag_items 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_tag_items. 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_tag_items 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 →