get_tasks_changed_since

List tasks changed since an ISO timestamp.

SERVERTodos SOURCE@hasna/todos

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/todos/get-tasks-changed-since.md

WHAT IT DOES

What get_tasks_changed_since does on Todos

AI agents call get_tasks_changed_since to retrieve information from Todos without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why get_tasks_changed_since is rated Low

This tool retrieves or lists task data based on a timestamp filter. It performs a read-only query operation without creating, modifying, deleting, or executing anything. The use of 'List' in the description confirms it is a data retrieval function.

From the tool's definition Tool name 'get_tasks_changed_since' and description 'List tasks changed since an ISO timestamp' indicate a query/retrieval operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_tasks_changed_since safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Todos, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_tasks_changed_since, this is the rule to start with:

get_tasks_changed_since Allowed

get_tasks_changed_since is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_tasks_changed_since": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Todos, apply this rule, and every get_tasks_changed_since call is checked against it from then on.

FAQ

Questions about get_tasks_changed_since

What does the get_tasks_changed_since tool do? +

List tasks changed since an ISO timestamp. It is categorised as a Read tool in the Todos MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_tasks_changed_since? +

Register the Todos MCP server in PolicyLayer and add a rule for get_tasks_changed_since: 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 Todos. Nothing to install.

What risk level is get_tasks_changed_since? +

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

Can I rate-limit get_tasks_changed_since? +

Yes. Add a rate_limit block to the get_tasks_changed_since 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_tasks_changed_since completely? +

Set action: deny in the PolicyLayer policy for get_tasks_changed_since. 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_tasks_changed_since? +

get_tasks_changed_since is provided by the Todos MCP server (@hasna/todos). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Todos, and thousands of servers like it.

This server

All 528 Todos tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →