issue_api_key · ThinAir Data MCP: Risk & Policy

WHAT IT DOES

What issue_api_key does on ThinAir Data

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

WHY IT NEEDS A POLICY

Why issue_api_key needs a policy

Issuing API keys is a reversible write action that creates new credentials. While sensitive, it does not permanently destroy data (Destructive), move money (Financial), or execute arbitrary code (Execute).

From the tool's definition Tool description states 'Issue a fresh ta_data_* API key for your current tenant' — directly creates new credentials. The mention of 'pasting into /add-database or configuring a separate integration' confirms this generates new authentication material.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

issue_api_key Rate-limited

issue_api_key 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": {
    "issue_api_key": {
      "limits": [
        {
          "counter": "issue_api_key_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 ThinAir Data, so you can run agents against it safely.

FAQ

Questions about issue_api_key

What does the issue_api_key tool do? +

Issue a fresh ta_data_* API key for your current tenant. Useful for pasting into /add-database or configuring a separate integration. Rate-limited to 5 issuances per tenant per day. It is categorised as a Write tool in the ThinAir Data MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on issue_api_key? +

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

What risk level is issue_api_key? +

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

Can I rate-limit issue_api_key? +

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

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

issue_api_key is provided by the ThinAir Data MCP server (thinairtelematics/thinair-data). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.