get_project_by_id

THE RISK

Low Risk

Why get_project_by_id needs a policy

This tool retrieves project information by ID. It performs a query/fetch operation without modifying, deleting, or executing any actions. The read-only nature places it in the Read category with low severity, as it has no destructive blast radius.

From the tool's definition Tool name 'get_project_by_id' and description 'Get a project by ID' indicate a retrieval operation with no side effects.

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

POLICY

How to control get_project_by_id

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

policy.json

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

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

Create a free account and register Ticktick — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Ticktick tools

Destructive delete_project Delete a project Destructive delete_task Delete a task Destructive batch_update_tasks Batch create, update, and/or delete multiple tasks in a single request Write complete_task Complete a task Write create_project Create a new project Write create_task Create a new task Write update_project Update an existing project Write update_task Update an existing task

All 16 Ticktick tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_project_by_id

What does the get_project_by_id tool do? +

Get a project by ID. It is categorised as a Read tool in the Ticktick MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_project_by_id? +

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

What risk level is get_project_by_id? +

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

Can I rate-limit get_project_by_id? +

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

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

get_project_by_id is provided by the Ticktick MCP server (@alexarevalo.ai/mcp-server-ticktick). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Ticktick tool call.

Start from Ticktick, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →