Get a task by ID for the current Cloud Redis account
AI agents call get-task-by-id to retrieve information from Redis Cloud API MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves task information from Redis Cloud by ID. The verb 'Get' combined with the read-only nature (fetching existing data) classifies this as a Read operation. No data is created, modified, deleted, or financial operations are performed. The severity is low as unauthorized access to task metadata poses minimal risk compared to destructive or financial operations.
From the tool's definition Tool name 'get-task-by-id' and description 'Get a task by ID' indicate a retrieval operation with no modification or side effects.
Documented attack patterns abuse exactly the kind of access get-task-by-id gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Redis Cloud API MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get-task-by-id:
{
"version": "1",
"default": "deny",
"tools": {
"get-task-by-id": {}
}
}get-task-by-id 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 a task by ID for the current Cloud Redis account. It is categorised as a Read tool in the Redis Cloud API MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Redis Cloud API MCP Server MCP server in PolicyLayer and add a rule for get-task-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 Redis Cloud API MCP Server. Nothing to install.
get-task-by-id 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-task-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.
Set action: deny in the PolicyLayer policy for get-task-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.
get-task-by-id is provided by the Redis Cloud API MCP Server MCP server (redis/mcp-redis-cloud). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 18 Redis Cloud API MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
18 Redis Cloud API MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.