AI agents call agentGet to retrieve information from Mcp Taskade without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries data about a specific agent by its identifier. It performs no modifications, deletions, or external operations. The blast radius of misuse is minimal—an attacker could only exfiltrate information about an agent, not modify or delete it.
From the tool's definition Tool name 'agentGet' and description 'Get agent with id' indicate a retrieval operation with no side effects. The verb 'Get' and the context of sibling tools (many of which are Create/Remove/Update operations) confirms this is a read-only query.
Documented attack patterns abuse exactly the kind of access agentGet gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Taskade, and nothing reaches the server without passing your rules. This is the rule we recommend for agentGet:
{
"version": "1",
"default": "deny",
"tools": {
"agentGet": {}
}
}agentGet 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 agent with id. It is categorised as a Read tool in the Mcp Taskade MCP Server, which means it retrieves data without modifying state.
Register the Mcp Taskade MCP server in PolicyLayer and add a rule for agentGet: 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 Mcp Taskade. Nothing to install.
agentGet 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 agentGet 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 agentGet. 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.
agentGet is provided by the Mcp Taskade MCP server (taskade/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 57 Mcp Taskade tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
57 Mcp Taskade tools catalogued and risk-classified — across an index of 42,500+ MCP servers.