get_session_context

πŸš€ [μƒˆ λŒ€ν™”/μ„Έμ…˜ μ‹œμž‘ μ‹œ μžλ™ μ‹€ν–‰ ꢌμž₯] 이전 μ„Έμ…˜μ˜ λ©”λͺ¨λ¦¬, 지식 κ·Έλž˜ν”„, 졜근 μž‘μ—… 내역을 ν•œ λ²ˆμ— μ‘°νšŒν•©λ‹ˆλ‹€. 이 λ„κ΅¬λŠ” μƒˆλ‘œμš΄ λŒ€ν™”λ₯Ό μ‹œμž‘ν•  λ•Œ κ°€μž₯ λ¨Όμ € μ‹€ν–‰ν•˜λ©΄ μ’‹μŠ΅λ‹ˆλ‹€. ν”„λ‘œμ νŠΈμ˜ μ»¨ν…μŠ€νŠΈλ₯Ό λΉ λ₯΄κ²Œ νŒŒμ•…ν•  수 μžˆμŠ΅λ‹ˆλ‹€. ν‚€μ›Œλ“œ: μ„Έμ…˜ μ‹œμž‘, μ»¨ν…μŠ€νŠΈ, 이전 μž‘μ—…, session start, context, previous work, what did we do μ‚¬μš© μ˜ˆμ‹œ: -

Server Hi-AI su-record/hi-ai
Category Read
Risk class Low
Parameters 00 required

What get_session_context does on Hi-AI

AI agents call get_session_context to retrieve information from Hi-AI without modifying anything β€” typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_session_context needs a policy

Even though get_session_context only reads data, uncontrolled read access leaks sensitive information and racks up API costs β€” an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Questions about get_session_context

What does the get_session_context tool do? +

πŸš€ [μƒˆ λŒ€ν™”/μ„Έμ…˜ μ‹œμž‘ μ‹œ μžλ™ μ‹€ν–‰ ꢌμž₯] 이전 μ„Έμ…˜μ˜ λ©”λͺ¨λ¦¬, 지식 κ·Έλž˜ν”„, 졜근 μž‘μ—… 내역을 ν•œ λ²ˆμ— μ‘°νšŒν•©λ‹ˆλ‹€. 이 λ„κ΅¬λŠ” μƒˆλ‘œμš΄ λŒ€ν™”λ₯Ό μ‹œμž‘ν•  λ•Œ κ°€μž₯ λ¨Όμ € μ‹€ν–‰ν•˜λ©΄ μ’‹μŠ΅λ‹ˆλ‹€. ν”„λ‘œμ νŠΈμ˜ μ»¨ν…μŠ€νŠΈλ₯Ό λΉ λ₯΄κ²Œ νŒŒμ•…ν•  수 μžˆμŠ΅λ‹ˆλ‹€. ν‚€μ›Œλ“œ: μ„Έμ…˜ μ‹œμž‘, μ»¨ν…μŠ€νŠΈ, 이전 μž‘μ—…, session start, context, previous work, what did we do μ‚¬μš© μ˜ˆμ‹œ: -. It is categorised as a Read tool in the Hi-AI MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_session_context? +

Register the Hi-AI MCP server in PolicyLayer and add a rule for get_session_context: 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 Hi-AI. Nothing to install.

What risk level is get_session_context? +

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

Can I rate-limit get_session_context? +

Yes. Add a rate_limit block to the get_session_context 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_context completely? +

Set action: deny in the PolicyLayer policy for get_session_context. 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_context? +

get_session_context is provided by the Hi-AI MCP server (su-record/hi-ai). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.