List completed tasks from the Logbook.
AI agents call list_logbook to retrieve information from Things Cloud MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only queries and retrieves already-completed tasks from a logbook—a read-only operation with no side effects. Even in the context of a task management system, listing completed items poses minimal risk. The severity is low because misuse would only expose task history data without enabling destructive or financial actions.
From the tool's definition Tool name 'list_logbook' and description 'List completed tasks from the Logbook' indicate retrieval of historical data with no modification or deletion capability.
Attacks that exploit this kind of access
List completed tasks from the Logbook. It is categorised as a Read tool in the Things Cloud MCP MCP Server, which means it retrieves data without modifying state.
Register the Things Cloud MCP server in PolicyLayer and add a rule for list_logbook: 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 Things Cloud MCP. Nothing to install.
list_logbook 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_logbook 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_logbook. 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_logbook is provided by the Things Cloud MCP server (nkootstra/things). 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 →