Returns detailed information for a single task including subtasks, notes, blockers, and related memories.
AI agents call get_task to retrieve information from Memory Pickle MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries task information (details, subtasks, notes, blockers, memories) with no side effects or state changes. It is a straightforward Read operation. Severity is low because exposing project/task metadata poses minimal risk; the data is already known to the system and retrieval cannot cause harm.
From the tool's definition Tool name 'get_task' and description 'Returns detailed information for a single task' indicates retrieval of data without modification. No language suggesting creation, deletion, or execution of operations.
Documented attack patterns abuse exactly the kind of access get_task gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Memory Pickle MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_task:
{
"version": "1",
"default": "deny",
"tools": {
"get_task": {}
}
} get_task 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.
Returns detailed information for a single task including subtasks, notes, blockers, and related memories. It is categorised as a Read tool in the Memory Pickle MCP MCP Server, which means it retrieves data without modifying state.
Register the Memory Pickle MCP server in PolicyLayer and add a rule for get_task: 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 Memory Pickle MCP. Nothing to install.
get_task 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 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. 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 is provided by the Memory Pickle MCP server (justar96/memory-pickle). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Memory Pickle MCP, 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.
13 Memory Pickle MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.