get_session_profile

Get the efficiency profile for the current session. Shows total calls, cost, latency, redundancy, and optimization suggestions.

SERVERNodebench SOURCEnodebench-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-homenshum-nodebench/get-session-profile.md

WHAT IT DOES

What get_session_profile does on Nodebench

AI agents call get_session_profile 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.

RISK

Why get_session_profile is rated Low

This tool retrieves and queries session profiling data (efficiency metrics, costs, latency statistics). It has no side effects, does not modify state, execute code, delete data, or commit financial transactions. It is a straightforward read operation that provides observability into session performance.

From the tool's definition Tool description states it 'Shows total calls, cost, latency, redundancy, and optimization suggestions' — purely retrieving session metrics and analytics data with no modification, deletion, or execution of external operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_session_profile 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_session_profile, this is the rule to start with:

get_session_profile Allowed

get_session_profile is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_session_profile": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Nodebench, apply this rule, and every get_session_profile call is checked against it from then on.

FAQ

Questions about get_session_profile

What does the get_session_profile tool do? +

Get the efficiency profile for the current session. Shows total calls, cost, latency, redundancy, and optimization suggestions. It is categorised as a Read tool in the Nodebench MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_session_profile? +

Register the Nodebench MCP server in PolicyLayer and add a rule for get_session_profile: 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.

What risk level is get_session_profile? +

get_session_profile is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_session_profile? +

Yes. Add a rate_limit block to the get_session_profile 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.

How do I block get_session_profile completely? +

Set action: deny in the PolicyLayer policy for get_session_profile. 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.

What MCP server provides get_session_profile? +

get_session_profile 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.

KEEP EXPLORING

More on Nodebench, and thousands of servers like it.

This server

All 824 Nodebench tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →