proma_knowledge_document
Write one approved outline item. Prefer targetRef from status and pageRef/quote evidence from pages read in this run. Supply admission to assess reuse value, business completeness and evidence; saved does not mean eligible. User quotes must be current or host-issued task userEvidenceId. The host ...
This record as markdown: /tools/dutydeck/proma-knowledge-document.md
What proma_knowledge_document does on DutyDeck
AI agents invoke proma_knowledge_document to trigger actions in DutyDeck. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why proma_knowledge_document is rated High
proma_knowledge_document triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.
Attacks that exploit this kind of access
The rule that runs proma_knowledge_document safely
PolicyLayer is an MCP gateway: it sits between your AI agents and DutyDeck, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For proma_knowledge_document, this is the rule to start with:
proma_knowledge_document stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect DutyDeck, apply this rule, and every proma_knowledge_document call is checked against it from then on.
Questions about proma_knowledge_document
Write one approved outline item. Prefer targetRef from status and pageRef/quote evidence from pages read in this run. Supply admission to assess reuse value, business completeness and evidence; saved does not mean eligible. User quotes must be current or host-issued task userEvidenceId. The host revalidates versions, permissions and quotes before the transaction. It is categorised as a Execute tool in the DutyDeck MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the DutyDeck MCP server in PolicyLayer and add a rule for proma_knowledge_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 DutyDeck. Nothing to install.
proma_knowledge_document is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the proma_knowledge_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 proma_knowledge_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.
proma_knowledge_document is provided by the DutyDeck MCP server (taokoplay/DutyDeck). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on DutyDeck, and thousands of servers like it.
Across the catalogue