Get articles written by a specific user.
AI agents call get_items_by_user 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 publicly accessible article metadata written by a user. It performs a query operation with no capability to modify, delete, or execute actions. The blast radius of misuse is minimal—an attacker could enumerate articles by user but cannot alter content, delete data, or trigger external operations. Classified as Read with low severity.
From the tool's definition Tool name 'get_items_by_user' and description 'Get articles written by a specific user' indicate data retrieval with no modification or side effects. Server description confirms it enables 'searching and browsing Qiita articles' as read-only operations.
Attacks that exploit this kind of access
Get articles written by a specific user. 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_items_by_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 MCP Server. Nothing to install.
get_items_by_user 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_items_by_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 get_items_by_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.
get_items_by_user 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 →