set_task_priority
AI agents use set_task_priority to create or update resources in RTM MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your RTM MCP Server environment.
This tool modifies existing task metadata (priority level) in a task management system. It's a Write operation because it creates or modifies data reversibly—priority changes can be undone or changed again. It's not Read (doesn't just retrieve), Execute (doesn't run code/commands), Destructive (doesn't delete), or Financial (no money involved).
From the tool's definition Tool name 'set_task_priority' and server context describing 'task manipulation, including priority settings'. The tool modifies task properties (priority) reversibly without deleting or executing external code.
Attacks that exploit this kind of access
set_task_priority. It is categorised as a Write tool in the RTM MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the RTM MCP Server MCP server in PolicyLayer and add a rule for set_task_priority: 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 RTM MCP Server. Nothing to install.
set_task_priority is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the set_task_priority 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 set_task_priority. 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.
set_task_priority is provided by the RTM MCP Server MCP server (ljadach/rtm-mcp). 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 →