Ingest a cardiology document (PDF path or raw text) and extract draft entities/relationships.
AI agents use ingest_document to create or update resources in Cardiology Knowledge Graph MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Cardiology Knowledge Graph MCP environment.
This tool reads a document and writes extracted entities/relationships as draft data into the knowledge graph. It creates new data (Write) rather than simply reading, but does not irreversibly destroy or execute arbitrary code. The medical context raises severity since incorrect extraction could introduce erroneous clinical data, but drafts are presumably reversible.
From the tool's definition 'Ingest a cardiology document (PDF path or raw text) and extract draft entities/relationships'
Attacks that exploit this kind of access
Ingest a cardiology document (PDF path or raw text) and extract draft entities/relationships. It is categorised as a Write tool in the Cardiology Knowledge Graph MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Cardiology Knowledge Graph MCP server in PolicyLayer and add a rule for ingest_document: 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 Cardiology Knowledge Graph MCP. Nothing to install.
ingest_document 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 ingest_document 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 ingest_document. 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.
ingest_document is provided by the Cardiology Knowledge Graph MCP server (ryoureddy/cardiology-knowledge-graph-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →