Search for contacts in Autotask. Returns 25 results per page by default. Use page parameter for more results.
AI agents call autotask_search_contacts to retrieve information from Autotask 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/queries contact data from Autotask without side effects. It is a standard read operation that returns search results. The mention of pagination confirms it is a retrieval mechanism only. No data is created, modified, deleted, or executed.
From the tool's definition Tool name contains 'search' and description explicitly states 'Search for contacts in Autotask' with pagination support. No modification, deletion, or execution of external actions occurs.
Attacks that exploit this kind of access
Search for contacts in Autotask. Returns 25 results per page by default. Use page parameter for more results. It is categorised as a Read tool in the Autotask MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Autotask MCP Server MCP server in PolicyLayer and add a rule for autotask_search_contacts: 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 Autotask MCP Server. Nothing to install.
autotask_search_contacts 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 autotask_search_contacts 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 autotask_search_contacts. 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.
autotask_search_contacts is provided by the Autotask MCP Server MCP server (ticnine/autotask-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 →