Get the site configuration record(s) for a company in Autotask. Site configurations contain tenant-defined fields used to track per-company configuration data. Call this first to discover which fields are available before calling autotask_update_company_site_configuration.
AI agents call autotask_get_company_site_configuration 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 configuration data for discovery purposes only. The description emphasizes it is called 'first' before updates, indicating it is informational and read-only. No data creation, modification, deletion, code execution, or financial operations occur. Blast radius is minimal as misuse only exposes existing configuration data.
From the tool's definition Tool name 'autotask_get_company_site_configuration' and description explicitly states 'Get the site configuration record(s)' with purpose to 'discover which fields are available'. This is a retrieval operation with no side effects.
Attacks that exploit this kind of access
Get the site configuration record(s) for a company in Autotask. Site configurations contain tenant-defined fields used to track per-company configuration data. Call this first to discover which fields are available before calling autotask_update_company_site_configuration. 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_get_company_site_configuration: 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_get_company_site_configuration 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_get_company_site_configuration 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_get_company_site_configuration. 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_get_company_site_configuration 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 →