autotask_update_company_site_configuration

WHAT IT DOES

What autotask_update_company_site_configuration does on Autotask MCP Server

AI agents use autotask_update_company_site_configuration to create or update resources in Autotask MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Autotask MCP Server environment.

WHY IT NEEDS A POLICY

Why autotask_update_company_site_configuration needs a policy

This tool creates or modifies data reversibly by updating configuration records for company sites. While it modifies settings that could have downstream operational impacts, the changes are reversible (fields can be updated again).

From the tool's definition Tool description states it "Update[s] fields on a company site configuration record" and requires passing "an updates object containing the fields to change." This is explicitly a modification operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

autotask_update_company_site_configuration Rate-limited

autotask_update_company_site_configuration stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "autotask_update_company_site_configuration": {
      "limits": [
        {
          "counter": "autotask_update_company_site_configuration_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Autotask MCP Server, so you can run agents against it safely.

FAQ

Questions about autotask_update_company_site_configuration

What does the autotask_update_company_site_configuration tool do? +

Update fields on a company site configuration record. The set of available fields is tenant-defined, so callers should first call autotask_get_company_site_configuration to discover the available field names and current values for the company. Pass the site configuration record id (not the company id) along with an updates object containing the fields to change. It is categorised as a Write tool in the Autotask MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on autotask_update_company_site_configuration? +

Register the Autotask MCP Server MCP server in PolicyLayer and add a rule for autotask_update_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.

What risk level is autotask_update_company_site_configuration? +

autotask_update_company_site_configuration is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit autotask_update_company_site_configuration? +

Yes. Add a rate_limit block to the autotask_update_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.

How do I block autotask_update_company_site_configuration completely? +

Set action: deny in the PolicyLayer policy for autotask_update_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.

What MCP server provides autotask_update_company_site_configuration? +

autotask_update_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.