business_intake · Inkwell MCP Server MCP: Risk & Policy

WHAT IT DOES

What business_intake does on Inkwell MCP Server

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

WHY IT NEEDS A POLICY

Why business_intake needs a policy

The tool creates multiple structured wiki pages to build a business intelligence profile. This is a Write operation (creating/organizing data reversibly) with medium severity since it populates a customer wiki with potentially sensitive business intelligence data, but does not execute code, delete data, or involve financial transactions.

From the tool's definition Creates interlinked wiki pages covering company profile, services, audience, competitors, brand voice, and channels

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

business_intake Rate-limited

business_intake 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": {
    "business_intake": {
      "limits": [
        {
          "counter": "business_intake_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 Inkwell MCP Server, so you can run agents against it safely.

FAQ

Questions about business_intake

What does the business_intake tool do? +

Gather business intelligence and build a structured wiki about a customer. This is the first tool to call when onboarding a new business. Creates interlinked wiki pages covering company profile, services, audience, competitors, brand voice, and channels. It is categorised as a Write tool in the Inkwell 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 business_intake? +

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

What risk level is business_intake? +

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

Can I rate-limit business_intake? +

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

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

business_intake is provided by the Inkwell MCP Server MCP server (mumega-com/inkwell). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.