指定されたユーザーのストック一覧を取得します
AI agents call get_user_stocks 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 (a user's stock/bookmark list) from Qiita without modifying, executing, deleting, or creating any content. It is a read-only operation with minimal risk even if misused, as it only exposes information already accessible through normal API queries.
From the tool's definition Tool name 'get_user_stocks' and description '指定されたユーザーのストック一覧を取得します' (retrieve a list of stocks/bookmarks for a specified user) indicate a 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_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 API 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 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 →