Get details of specific rows by IDs.
AI agents call appflowy_get_row_details to retrieve information from AppFlowy MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves row details by ID, matching the Read category definition: 'retrieves or queries data; no side effects.' The blast radius of misuse is minimal—an agent could access rows it shouldn't, but cannot modify, delete, or execute operations. The low severity reflects that data exposure via read access is less damaging than write, destructive, or financial operations.
From the tool's definition Tool name 'appflowy_get_row_details' and description 'Get details of specific rows by IDs' indicate retrieval of data with the verb 'Get', which is a read-only query operation with no modification or side effects.
Attacks that exploit this kind of access
Get details of specific rows by IDs. It is categorised as a Read tool in the AppFlowy MCP MCP Server, which means it retrieves data without modifying state.
Register the AppFlowy MCP server in PolicyLayer and add a rule for appflowy_get_row_details: 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 AppFlowy MCP. Nothing to install.
appflowy_get_row_details 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 appflowy_get_row_details 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 appflowy_get_row_details. 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.
appflowy_get_row_details is provided by the AppFlowy MCP server (weironz/appflowy_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 →