nb_filter_tool_activity
Filter the MCP ledger by tool name, date, or status.
This record as markdown: /tools/io-github-homenshum-nodebench/nb-filter-tool-activity.md
What nb_filter_tool_activity does on Nodebench
AI agents call nb_filter_tool_activity 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 nb_filter_tool_activity is rated Low
This tool retrieves and filters records from a ledger based on search criteria (tool name, date, status). Filtering is a read-only operation that queries data without creating, modifying, deleting, or executing actions. The low severity reflects minimal risk—an AI agent misusing this can only over-query or access unintended ledger records, not cause irreversible harm.
From the tool's definition Tool name 'nb_filter_tool_activity' and description 'Filter the MCP ledger by tool name, date, or status' indicate querying/filtering existing data with no modification capability.
Attacks that exploit this kind of access
The rule that runs nb_filter_tool_activity 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 nb_filter_tool_activity, this is the rule to start with:
nb_filter_tool_activity 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 nb_filter_tool_activity call is checked against it from then on.
Questions about nb_filter_tool_activity
Filter the MCP ledger by tool name, date, or status. 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 nb_filter_tool_activity: 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.
nb_filter_tool_activity 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 nb_filter_tool_activity 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 nb_filter_tool_activity. 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.
nb_filter_tool_activity 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