Call this when query_knowledge_base returned no documented guidance for a decision you need to make.
AI agents use resolve_gap to create or update resources in MarkdownLM MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MarkdownLM MCP Server environment.
The tool appears to fill in missing documentation or governance guidance when none exists, implying it writes or creates new entries in the knowledge base/memory layer. Since it resolves an undocumented gap, it likely persists new rules or decisions. The description is sparse, so confidence is moderate.
From the tool's definition 'resolve_gap' - called when 'query_knowledge_base returned no documented guidance for a decision you need to make'
Documented attack patterns abuse exactly the kind of access resolve_gap gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MarkdownLM MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for resolve_gap:
{
"version": "1",
"default": "deny",
"tools": {
"resolve_gap": {
"limits": [
{
"counter": "resolve_gap_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}resolve_gap 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.
Call this when query_knowledge_base returned no documented guidance for a decision you need to make. It is categorised as a Write tool in the MarkdownLM MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MarkdownLM MCP Server MCP server in PolicyLayer and add a rule for resolve_gap: 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 MarkdownLM MCP Server. Nothing to install.
resolve_gap 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 resolve_gap 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 resolve_gap. 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.
resolve_gap is provided by the MarkdownLM MCP Server MCP server (markdownlm/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MarkdownLM MCP Server, 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.
3 MarkdownLM MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.