AI agents call pingcode_get_workitem_states to retrieve information from Pingcode 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 state information from PingCode's work item system. It performs a lookup operation to list available states or resolve a state name to its corresponding ID. There are no side effects, data modifications, code execution, or destructive operations. It is a straightforward read operation that fits the 'Read' category with low risk.
From the tool's definition Tool name 'pingcode_get_workitem_states' and description indicate retrieval of work item states/status list or querying status IDs by name. The verbs '获取' (get/retrieve) and '查询' (query) confirm read-only data retrieval with no modification or execution.
Attacks that exploit this kind of access
当需要获取工作项状态列表的时候，或者需要通过状态名字查询某个状态ID的时候，调用此工具。. It is categorised as a Read tool in the Pingcode MCP Server, which means it retrieves data without modifying state.
Register the Pingcode MCP server in PolicyLayer and add a rule for pingcode_get_workitem_states: 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 Pingcode. Nothing to install.
pingcode_get_workitem_states 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 pingcode_get_workitem_states 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 pingcode_get_workitem_states. 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.
pingcode_get_workitem_states is provided by the Pingcode MCP server (pingcode-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 →