Get current organization context (selected company and dealer). Use this to check which company/dealer is currently active.
AI agents call get_user_context to retrieve information from StockSpark MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves contextual metadata about the current user's organization and active dealer selection. It performs no mutations, executes no code, and has no side effects. The read-only nature and limited blast radius (context information disclosure) place it in the Read category with low severity.
From the tool's definition Tool name 'get_user_context' and description 'Get current organization context (selected company and dealer).
Attacks that exploit this kind of access
Get current organization context (selected company and dealer). Use this to check which company/dealer is currently active. It is categorised as a Read tool in the StockSpark MCP Server MCP Server, which means it retrieves data without modifying state.
Register the StockSpark MCP Server MCP server in PolicyLayer and add a rule for get_user_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 StockSpark MCP Server. Nothing to install.
get_user_context 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_user_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.
Set action: deny in the PolicyLayer policy for get_user_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.
get_user_context is provided by the StockSpark MCP Server MCP server (loukach/stockspark-mcp-poc). 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 →