Imports data from markdown files into ConPort.
AI agents use import_markdown_to_conport to create or update resources in SDOF Knowledge Base — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your SDOF Knowledge Base environment.
This tool's primary function is to ingest external markdown data and persist it into the ConPort system. This is a reversible, non-destructive modification operation. It does not execute arbitrary code, delete data, or move financial assets.
From the tool's definition Tool description states it 'Imports data from markdown files into ConPort,' which creates or modifies data in the system. The verb 'imports' combined with 'into ConPort' indicates data creation or modification (write operation).
Attacks that exploit this kind of access
Imports data from markdown files into ConPort. It is categorised as a Write tool in the SDOF Knowledge Base MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the SDOF Knowledge Base MCP server in PolicyLayer and add a rule for import_markdown_to_conport: 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 SDOF Knowledge Base. Nothing to install.
import_markdown_to_conport 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 import_markdown_to_conport 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 import_markdown_to_conport. 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.
import_markdown_to_conport is provided by the SDOF Knowledge Base MCP server (tgf-between-your-legs/sdof-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 →