proma_knowledge_submit
Submit durable knowledge grounded in source pages actually read during this run or in an exact quote from the current user message. Source candidates remain drafts. Empty source candidates may mark a fully reviewed batch processed. The host revalidates every quote, version and permission before p...
This record as markdown: /tools/dutydeck/proma-knowledge-submit.md
What proma_knowledge_submit does on DutyDeck
AI agents use proma_knowledge_submit to create or update resources in DutyDeck, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your DutyDeck environment.
Why proma_knowledge_submit is rated Medium
An AI agent can call proma_knowledge_submit faster than any human can review: one bad instruction and it creates or modifies resources in DutyDeck by the hundred, each call as confident as the last.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs proma_knowledge_submit 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_submit, this is the rule to start with:
proma_knowledge_submit 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.
The button opens the PolicyLayer dashboard: create your workspace, connect DutyDeck, apply this rule, and every proma_knowledge_submit call is checked against it from then on.
Questions about proma_knowledge_submit
Submit durable knowledge grounded in source pages actually read during this run or in an exact quote from the current user message. Source candidates remain drafts. Empty source candidates may mark a fully reviewed batch processed. The host revalidates every quote, version and permission before publishing. It is categorised as a Write tool in the DutyDeck MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the DutyDeck MCP server in PolicyLayer and add a rule for proma_knowledge_submit: 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_submit 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 proma_knowledge_submit 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_submit. 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_submit 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.
This server
Across the catalogue