getSourceRegistry
Get the source registry for a domain, showing all tracked data sources with freshness and reliability scores.
This record as markdown: /tools/io-github-homenshum-nodebench/getsourceregistry.md
What getSourceRegistry does on Nodebench
AI agents call getSourceRegistry 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 getSourceRegistry is rated Low
This is a straightforward read operation that retrieves and displays information about data sources (their registry entries, freshness scores, and reliability metrics). No data is modified, deleted, executed, or committed. The tool simply returns informational content about tracked sources.
From the tool's definition Tool name 'getSourceRegistry' and description 'Get the source registry for a domain, showing all tracked data sources with freshness and reliability scores' indicate a retrieval operation that queries existing registry data without modification.
Attacks that exploit this kind of access
The rule that runs getSourceRegistry 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 getSourceRegistry, this is the rule to start with:
getSourceRegistry 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 getSourceRegistry call is checked against it from then on.
Questions about getSourceRegistry
Get the source registry for a domain, showing all tracked data sources with freshness and reliability scores. 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 getSourceRegistry: 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.
getSourceRegistry 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 getSourceRegistry 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 getSourceRegistry. 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.
getSourceRegistry 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