generate_demo_workspace · Sanka MCP Server MCP

WHAT IT DOES

What generate_demo_workspace does on Sanka MCP Server

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

WHY IT NEEDS A POLICY

Why generate_demo_workspace needs a policy

The tool creates or seeds records in connected CRM and accounting systems (HubSpot/Salesforce), which is a Write operation. Severity is high rather than critical because the creation appears to be of demo/test data rather than direct financial transfers, though it could trigger downstream processes given the presence of invoice activation and payroll approval tools.

From the tool's definition Tool description states "Seed a Sanka workspace or create records directly in HubSpot/Salesforce" and "create records" — this creates data in external systems.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

generate_demo_workspace Rate-limited

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

FAQ

Questions about generate_demo_workspace

What does the generate_demo_workspace tool do? +

Seed a Sanka workspace or create records directly in HubSpot/Salesforce with a curated lead-to-cash demo. For direct provider creation, set target=. It is categorised as a Write tool in the Sanka 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 generate_demo_workspace? +

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

What risk level is generate_demo_workspace? +

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

Can I rate-limit generate_demo_workspace? +

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

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

generate_demo_workspace is provided by the Sanka MCP Server MCP server (sankahq/sanka-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.