Generate agent instructions for a task using template resolution hierarchy (task → task list → project → fallback)
AI agents call get_agent_instructions to retrieve information from TasksMultiServer without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves or computes instructions by traversing a template hierarchy but does not create, modify, delete, or execute actions. It is fundamentally a read operation that queries task metadata to produce instructions. No side effects or irreversible changes occur.
From the tool's definition Tool name is 'get_agent_instructions' and description states it 'Generate agent instructions for a task using template resolution hierarchy'.
Attacks that exploit this kind of access
Generate agent instructions for a task using template resolution hierarchy (task → task list → project → fallback). It is categorised as a Read tool in the TasksMultiServer MCP Server, which means it retrieves data without modifying state.
Register the TasksMultiServer MCP server in PolicyLayer and add a rule for get_agent_instructions: 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 TasksMultiServer. Nothing to install.
get_agent_instructions 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_agent_instructions 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_agent_instructions. 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_agent_instructions is provided by the TasksMultiServer MCP server (keyurgolani/tasksmultiserver). 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 →