get_source_trust_policy
Return the source-level permission and trust policy for storage, summarization, and export across private and public source types.
This record as markdown: /tools/io-github-homenshum-nodebench/get-source-trust-policy.md
What get_source_trust_policy does on Nodebench
AI agents call get_source_trust_policy to retrieve information from Nodebench without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_source_trust_policy is rated Low
This is a read-only operation that retrieves and returns policy information for sources. No side effects, modifications, or executions occur. The tool simply exposes existing trust and permission policies, making it a Read category tool with low severity since policy retrieval alone poses minimal risk to system integrity.
From the tool's definition Tool name includes 'get_' prefix and description uses 'Return', indicating data retrieval. The tool retrieves policy configuration information about source-level permissions and trust settings—it queries existing policy state without modifying, deleting, or…
Attacks that exploit this kind of access
The rule that runs get_source_trust_policy 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 get_source_trust_policy, this is the rule to start with:
get_source_trust_policy is read-only, so it stays allowed. 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 get_source_trust_policy call is checked against it from then on.
Questions about get_source_trust_policy
Return the source-level permission and trust policy for storage, summarization, and export across private and public source types. It is categorised as a Read tool in the Nodebench MCP Server, which means it retrieves data without modifying state.
Register the Nodebench MCP server in PolicyLayer and add a rule for get_source_trust_policy: 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.
get_source_trust_policy is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_source_trust_policy 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 get_source_trust_policy. 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.
get_source_trust_policy 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