ai_chat

SERVERIconnect SOURCEiconnect-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-heznpc-iconnect/ai-chat.md

WHAT IT DOES

What ai_chat does on Iconnect

AI agents invoke ai_chat to trigger actions in Iconnect. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

RISK

Why ai_chat is rated High

This tool executes an on-device AI model with user-supplied input. The effects depend entirely on the message content passed to the model, which could produce harmful outputs, trigger downstream actions, or be used to probe/manipulate the AI system. It spans Execute territory because it runs an AI inference session rather than simply reading static data.

From the tool's definition 'Send a message to an on-device AI session using Apple Foundation Models' — triggers an external AI model execution with arbitrary message input

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs ai_chat safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Iconnect, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For ai_chat, this is the rule to start with:

ai_chat Rate-limited

ai_chat stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "ai_chat": {
      "limits": [
        {
          "counter": "ai_chat_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Iconnect, apply this rule, and every ai_chat call is checked against it from then on.

FAQ

Questions about ai_chat

What does the ai_chat tool do? +

Send a message to an on-device AI session using Apple Foundation Models. Note: each call creates a fresh session — sessionName is for caller-side tracking only, not server-side persistence. Requires macOS 26+. It is categorised as a Execute tool in the Iconnect MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on ai_chat? +

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

What risk level is ai_chat? +

ai_chat is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit ai_chat? +

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

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

ai_chat is provided by the Iconnect MCP server (iconnect-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Iconnect, and thousands of servers like it.

This server

All 279 Iconnect tools → High-risk tools on this server →

Across the catalogue

ai_chat on Percepta MCP Server → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →