Low Risk

get_logbook

Get completed todos from Logbook, defaults to last 7 days.

How to control get_logbook ↓

AI agents call get_logbook to retrieve information from Things 3 MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool retrieves already-completed task records from a logbook without modifying, deleting, or executing any operations. It is a simple data query operation with no destructive or side effects, fitting the 'Read' category. The severity is low as misuse would only expose personal task history data already under user control.

From the tool's definition Tool name 'get_logbook' and description 'Get completed todos from Logbook' indicate a read-only retrieval operation. The phrase 'Get completed todos from Logbook, defaults to last 7 days' confirms querying historical data with no modification or side effects.

Documented attack patterns abuse exactly the kind of access get_logbook gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Things 3 MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_logbook:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_logbook": {}
  }
}

get_logbook is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Things 3 MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the get_logbook tool do? +

Get completed todos from Logbook, defaults to last 7 days. It is categorised as a Read tool in the Things 3 MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_logbook? +

Register the Things 3 MCP Server MCP server in PolicyLayer and add a rule for get_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 3 MCP Server. Nothing to install.

What risk level is get_logbook? +

get_logbook is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_logbook? +

Yes. Add a rate_limit block to the get_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.

How do I block get_logbook completely? +

Set action: deny in the PolicyLayer policy for get_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.

What MCP server provides get_logbook? +

get_logbook is provided by the Things 3 MCP Server MCP server (rossshannon/things3-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Things 3 MCP Server tool call.

Deterministic rules across all 24 Things 3 MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

24 Things 3 MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.