AI agents call getCardContent to retrieve information from Heptabase MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves card content from Heptabase backups. Based on the server's stated purpose of allowing retrieval and analysis of backup data, getCardContent performs a read operation without side effects. Severity is medium due to the potential sensitivity of personal knowledge management data (like Heptabase cards), though the operation itself is non-destructive and read-only.
From the tool's definition Tool name 'getCardContent' and server description indicating the service 'allows AI assistants to search, retrieve, analyze, and export data from Heptabase backups.' This is a retrieval operation. The tool description is empty, limiting confidence.
Documented attack patterns abuse exactly the kind of access getCardContent 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 getCardContent:
{
"version": "1",
"default": "deny",
"tools": {
"getCardContent": {}
}
}getCardContent is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
getCardContent. It is categorised as a Read tool in the Heptabase MCP MCP Server, which means it retrieves data without modifying state.
Register the Heptabase MCP server in PolicyLayer and add a rule for getCardContent: 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.
getCardContent is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the getCardContent 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 getCardContent. 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.
getCardContent 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.