Retrieve complete details of a single log via GET /api/request-logs/{id}/. Returns full information including: - Full input/output content (input and output fields) - Type-specific fields based on log_type (chat, embedding, workflow, etc.) - Credit and budget check results (limit_info) - Evaluati...
AI agents call get_log_detail to retrieve information from Respan MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a Read category tool because it uses GET to query and retrieve existing log data. Severity is medium rather than low because logs may contain sensitive information (full input/output content, metadata, credit/budget details) that could be misused if an agent over-retrieves logs or accesses logs it shouldn't. However, it poses no direct destructive, financial, or code-execution risk.
From the tool's definition Tool retrieves 'complete details of a single log' via GET request. Returns 'full input/output content', 'metadata', 'evaluation scores'—all read operations with no modification.
Attacks that exploit this kind of access
Retrieve complete details of a single log via GET /api/request-logs/{id}/. Returns full information including: - Full input/output content (input and output fields) - Type-specific fields based on log_type (chat, embedding, workflow, etc.) - Credit and budget check results (limit_info) - Evaluation scores - Complete request/response metadata - Tool calls and function calling details The limit_info field shows: - is_allowed: Whether the request was allowed - limits: Array of limit checks (org_credits, customer_budget) - current_value: Balance before request - new_value: Balance after request - limit_value: Minimum required balance - is_within_limit: Whether check passed Use list_logs first to find the unique_id, then use this endpoint for full details. It is categorised as a Read tool in the Respan MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Respan MCP Server MCP server in PolicyLayer and add a rule for get_log_detail: 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 Respan MCP Server. Nothing to install.
get_log_detail 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_log_detail 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_log_detail. 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_log_detail is provided by the Respan MCP Server MCP server (respanai/respan-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →