Returns inline specs, syntax references, gotchas, and recipe matches for your task. Recommended before building — helps prevent syntax errors and hallucinated field names. Call this with a description of what you want to build to receive targeted Portals knowledge.
AI agents call get_context to retrieve information from Portals without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
query | string | Yes | Describe what you want to build or do. |
stage | string | — | Optional stage hint: setup, design, build, logic, validate, assets, settings. |
Parameters from the server's own tool schema.
get_context is a lookup/reference tool that provides documentation and guidance. It retrieves data (specs, syntax, recipes) with no side effects, state changes, or operations triggered. This is a classic Read category tool — informational only.
From the tool's definition Tool description states it 'Returns inline specs, syntax references, gotchas, and recipe matches' — purely retrieves and queries information without modifying or executing operations.
Risk signalsAccepts freeform code/query input (query)
Attacks that exploit this kind of access
Returns inline specs, syntax references, gotchas, and recipe matches for your task. Recommended before building — helps prevent syntax errors and hallucinated field names. Call this with a description of what you want to build to receive targeted Portals knowledge. It is categorised as a Read tool in the Portals MCP Server, which means it retrieves data without modifying state.
get_context accepts 2 parameters: query, stage. Required: query. The full parameter table on this page comes from the server's own tool schema.
Register the Portals MCP server in PolicyLayer and add a rule for get_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 Portals. Nothing to install.
get_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_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_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_context is provided by the Portals MCP server (portals-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 →