AI agents use exportWhiteboard to create or update resources in Heptabase MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Heptabase MCP environment.
Export operations create new data artifacts (exported files/formats) but are reversible—the original data remains unchanged. This qualifies as Write rather than Read (which would be passive retrieval). Severity is medium because unintended exports could leak sensitive data from whiteboards, but the action is not destructive or financial.
From the tool's definition Tool name 'exportWhiteboard' indicates data export functionality. Per the server description, the MCP service supports 'export data from Heptabase backups.' Export typically writes data to a new format or destination (e.g., file, archive).
Documented attack patterns abuse exactly the kind of access exportWhiteboard gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Heptabase MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for exportWhiteboard:
{
"version": "1",
"default": "deny",
"tools": {
"exportWhiteboard": {
"limits": [
{
"counter": "exportwhiteboard_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}exportWhiteboard 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.
Free to start. No card required.
exportWhiteboard. It is categorised as a Write tool in the Heptabase MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Heptabase MCP server in PolicyLayer and add a rule for exportWhiteboard: 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 Heptabase MCP. Nothing to install.
exportWhiteboard is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the exportWhiteboard 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.
Set action: deny in the PolicyLayer policy for exportWhiteboard. 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.
exportWhiteboard is provided by the Heptabase MCP server (larrystanley/heptabase-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Heptabase MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
14 Heptabase MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.