Get articles that a user has stocked (bookmarked).
AI agents call get_user_stocks 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 queries and returns a list of articles a user has bookmarked. It is a read-only operation that has no side effects, does not modify any data, and does not trigger external actions. It matches the Read category pattern of retrieving or querying data without side effects.
From the tool's definition Tool name 'get_user_stocks' and description 'Get articles that a user has stocked (bookmarked)' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
Get articles that a user has stocked (bookmarked). 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_user_stocks: 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_user_stocks 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_user_stocks 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_user_stocks. 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_user_stocks 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 →