maker_get_session_context

Return non-PII context the companion

SERVERCrow SOURCEkh0pper/crow

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/kh0pper-crow/maker-get-session-context.md

WHAT IT DOES

What maker_get_session_context does on Crow

AI agents call maker_get_session_context to retrieve information from Crow without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why maker_get_session_context is rated Low

This tool retrieves session context information without modifying, executing operations, or deleting data. The explicit non-PII constraint further limits potential harm. Classification as Read is appropriate for a context retrieval operation used to support AI assistant operations.

From the tool's definition Tool name 'maker_get_session_context' and description 'Return non-PII context the companion' indicate a retrieval operation that returns session context data (explicitly non-PII).

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs maker_get_session_context safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Crow, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For maker_get_session_context, this is the rule to start with:

maker_get_session_context Allowed

maker_get_session_context 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": {
    "maker_get_session_context": {}
  }
}

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

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

FAQ

Questions about maker_get_session_context

What does the maker_get_session_context tool do? +

Return non-PII context the companion. It is categorised as a Read tool in the Crow MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on maker_get_session_context? +

Register the Crow MCP server in PolicyLayer and add a rule for maker_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 Crow. Nothing to install.

What risk level is maker_get_session_context? +

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

Can I rate-limit maker_get_session_context? +

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

Set action: deny in the PolicyLayer policy for maker_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 maker_get_session_context? +

maker_get_session_context is provided by the Crow MCP server (kh0pper/crow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Crow, and thousands of servers like it.

This server

All 587 Crow 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 →