Get one transaction entry by entry_id. Use this before updating or deleting when you already know the ID.
AI agents call whooing_entry_detail to retrieve information from Whooing MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves a single transaction entry by its identifier. The operation is purely informational with no modifications to data. While the broader server includes destructive tools (whooing_delete_entry, whooing_bulk_add_entries), this specific tool performs only a read/fetch operation. The mention of use 'before updating or deleting' indicates it's a lookup helper, not an action tool itself.
From the tool's definition Tool description states 'Get one transaction entry by entry_id' — a retrieval operation with no side effects. Server description emphasizes 'read-only access' and 'query and analyze' capabilities.
Attacks that exploit this kind of access
Get one transaction entry by entry_id. Use this before updating or deleting when you already know the ID. It is categorised as a Read tool in the Whooing MCP MCP Server, which means it retrieves data without modifying state.
Register the Whooing MCP server in PolicyLayer and add a rule for whooing_entry_detail: 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 Whooing MCP. Nothing to install.
whooing_entry_detail 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 whooing_entry_detail 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 whooing_entry_detail. 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.
whooing_entry_detail is provided by the Whooing MCP server (jmjeong/whooing-mcp). 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 →