This record as markdown: /tools/kiln/get-session-log.md
What get_session_log does on Kiln
AI agents call get_session_log to retrieve information from Kiln without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_session_log is rated Low
Session logs are historical records typically accessed for monitoring or debugging. The 'get' prefix strongly suggests read-only access with no side effects. However, the empty description prevents verification of whether sensitive data might be exposed (which could elevate severity). Given the context of 3D printer control systems, logs may contain operational data but retrieval itself is non-destructive.
From the tool's definition Tool name 'get_session_log' indicates retrieval of session log data with no modification. Description is empty, limiting certainty about side effects.
Attacks that exploit this kind of access
The rule that runs get_session_log safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Kiln, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_session_log, this is the rule to start with:
get_session_log 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 Kiln, apply this rule, and every get_session_log call is checked against it from then on.
Questions about get_session_log
get_session_log is a read tool on the Kiln MCP server. It is categorised as a Read tool in the Kiln MCP Server, which means it retrieves data without modifying state.
Register the Kiln MCP server in PolicyLayer and add a rule for get_session_log: 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 Kiln. Nothing to install.
get_session_log 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_session_log 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_session_log. 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_session_log is provided by the Kiln MCP server (codeofaxel/Kiln). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Kiln, and thousands of servers like it.
This server
Across the catalogue