AI agents call get_todo_list to retrieve information from Mcp Pkm Logseq without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves a user's todo list from Logseq without any side effects. The server explicitly describes retrieval operations, and the tool name indicates a simple GET operation. No creation, modification, deletion, or external execution occurs.
From the tool's definition Tool name 'get_todo_list' and server description indicating 'retrieval of tagged notes and todo lists through Logseq's HTTP API' shows this retrieves data without modification.
Documented attack patterns abuse exactly the kind of access get_todo_list gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Pkm Logseq, and nothing reaches the server without passing your rules. This is the rule we recommend for get_todo_list:
{
"version": "1",
"default": "deny",
"tools": {
"get_todo_list": {}
}
}get_todo_list is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
get_todo_list. It is categorised as a Read tool in the Mcp Pkm Logseq MCP Server, which means it retrieves data without modifying state.
Register the Mcp Pkm Logseq MCP server in PolicyLayer and add a rule for get_todo_list: 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 Mcp Pkm Logseq. Nothing to install.
get_todo_list 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 get_todo_list 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 get_todo_list. 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.
get_todo_list is provided by the Mcp Pkm Logseq MCP server (ruliana/mcp-pkm-logseq). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mcp Pkm Logseq, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
3 Mcp Pkm Logseq tools catalogued and risk-classified — across an index of 43,000+ MCP servers.