nodebench.claims.submit_public
Submit a sourced public claim. The verifier rejects private sources, raw email/resume/private artifact text, and uncited claims.
This record as markdown: /tools/io-github-homenshum-nodebench/nodebench.claims.submit-public.md
What nodebench.claims.submit_public does on Nodebench
AI agents use nodebench.claims.submit_public to create or update resources in Nodebench, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Nodebench environment.
Why nodebench.claims.submit_public is rated Medium
The tool submits (creates/writes) a new public claim record. It does not delete data, execute code, or involve financial transactions. The verifier constraints (no private sources, must be cited) reduce but don't eliminate misuse risk — a bad actor could still submit false or misleading public claims at scale, hence medium severity.
From the tool's definition Submit a sourced public claim
Attacks that exploit this kind of access
The rule that runs nodebench.claims.submit_public safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Nodebench, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For nodebench.claims.submit_public, this is the rule to start with:
nodebench.claims.submit_public 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 Nodebench, apply this rule, and every nodebench.claims.submit_public call is checked against it from then on.
Questions about nodebench.claims.submit_public
Submit a sourced public claim. The verifier rejects private sources, raw email/resume/private artifact text, and uncited claims. It is categorised as a Write tool in the Nodebench MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Nodebench MCP server in PolicyLayer and add a rule for nodebench.claims.submit_public: 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 Nodebench. Nothing to install.
nodebench.claims.submit_public 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 nodebench.claims.submit_public 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 nodebench.claims.submit_public. 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.
nodebench.claims.submit_public is provided by the Nodebench MCP server (nodebench-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Nodebench, and thousands of servers like it.
This server
Across the catalogue