Exports ConPort data to markdown files.
AI agents use export_conport_to_markdown 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 writes data to the filesystem by creating or overwriting markdown files. It is a Write operation (file creation/modification). If it overwrites existing files without warning it could have mild destructive implications, but the primary action is writing output files. Severity is medium because it could overwrite existing files on disk, but it is generally reversible.
From the tool's definition Exports ConPort data to markdown files
Attacks that exploit this kind of access
Exports ConPort data to markdown files. 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 export_conport_to_markdown: 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.
export_conport_to_markdown 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 export_conport_to_markdown 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 export_conport_to_markdown. 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.
export_conport_to_markdown 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 →