AI agents call list_pending_items to retrieve information from Fichapao without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves pending items associated with a recipe version without modifying, deleting, or executing any operations. It is purely informational, making it a Read category risk with low severity since it only exposes data visibility with minimal blast radius if misused by an AI agent.
From the tool's definition Tool name 'list_pending_items' and description 'Lists open pending items of a technical sheet version' indicate a retrieval operation with no side effects. The verb 'list' and the read-only nature of querying pending items confirm this is a Read operation.
Attacks that exploit this kind of access
Lista pendencias abertas de uma versao da ficha tecnica. It is categorised as a Read tool in the Fichapao MCP Server, which means it retrieves data without modifying state.
Register the Fichapao MCP server in PolicyLayer and add a rule for list_pending_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 Fichapao. Nothing to install.
list_pending_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 list_pending_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 list_pending_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.
list_pending_items is provided by the Fichapao MCP server (kratos4ai/fichapao-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 →