log_tool_call
Log an MCP tool call for profiling. Called automatically by the NodeBench gateway to track tool usage patterns, cost, and latency. Returns whether the call was redundant.
This record as markdown: /tools/io-github-homenshum-nodebench/log-tool-call.md
What log_tool_call does on Nodebench
AI agents call log_tool_call 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 log_tool_call is rated Low
The tool is a logging and telemetry mechanism that captures call patterns and performance metrics. It has no side effects on user data or system state beyond writing immutable logs. The return value indicates redundancy detection, which is information-retrieval based.
From the tool's definition Logs tool calls for profiling, tracking usage patterns, cost, and latency; returns whether the call was redundant. This is purely observational—it reads/records metadata about tool calls without modifying data, executing code, or causing destructive effects.
Attacks that exploit this kind of access
The rule that runs log_tool_call 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 log_tool_call, this is the rule to start with:
log_tool_call 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 log_tool_call call is checked against it from then on.
Questions about log_tool_call
Log an MCP tool call for profiling. Called automatically by the NodeBench gateway to track tool usage patterns, cost, and latency. Returns whether the call was redundant. 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 log_tool_call: 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.
log_tool_call 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 log_tool_call 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 log_tool_call. 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.
log_tool_call 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