Medium Risk

autotask_create_company

Create new company

Part of the Autotask server.

autotask_create_company can modify Autotask data, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE AUTOTASK →

Free to start. No card required.

AI agents use autotask_create_company to create or modify resources in Autotask. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call autotask_create_company repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Autotask.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "autotask_create_company": {
      "limits": [
        {
          "counter": "autotask_create_company_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

See the full Autotask policy for all 24 tools.

Get this rule live on your own Autotask server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY AUTOTASK →

View all 24 tools →

These attack patterns abuse exactly the kind of access autotask_create_company gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so autotask_create_company only ever does what you allow.

SECURE AUTOTASK →

Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.

What does the autotask_create_company tool do? +

Create new company. It is categorised as a Write tool in the Autotask 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_create_company? +

Register the Autotask MCP server in PolicyLayer and add a rule for autotask_create_company: 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. Nothing to install.

What risk level is autotask_create_company? +

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

Can I rate-limit autotask_create_company? +

Yes. Add a rate_limit block to the autotask_create_company 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_create_company completely? +

Set action: deny in the PolicyLayer policy for autotask_create_company. 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_create_company? +

autotask_create_company is provided by the Autotask MCP server (oci:ghcr.io/wyre-technology/autotask-mcp:v2.28.3). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Autotask tool call.

Deterministic rules across all 24 Autotask tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.