Fast knowledge lookup. Returns specs for items, triggers, effects, systems, or recipes directly. Supports batch mode: pass 'terms' array (max 20) to look up multiple items in one call instead of making separate requests.
AI agents call lookup 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 |
|---|---|---|---|
term | string | — | Search term: item name, prefabName, $type, or keyword. E.g., 'cube', 'OnClickEvent', 'keypad'. |
type | string | — | Filter by entry type: item, trigger, effect, system, recipe, pattern. |
terms | array | — | Batch lookup: array of search terms (max 20). Returns results for each term in one call. Use instead of multiple single lookups. |
category | string | — | Filter by category: building, models, gameplay, media, lighting, display, interactive, effects, triggers, systems, interactions. |
Parameters from the server's own tool schema.
This tool retrieves and returns structured information (specs, recipes, system details) without creating, modifying, deleting, or executing any operations. It is a pure read operation that queries a knowledge base. No side effects or state changes are implied by the description. The batch mode capability does not change the fundamental nature of the operation—it remains a Read category tool.
From the tool's definition Tool description states 'Fast knowledge lookup. Returns specs for items, triggers, effects, systems, or recipes directly.' The verb 'Returns' and 'lookup' indicate data retrieval with no modification or side effects.
Attacks that exploit this kind of access
Fast knowledge lookup. Returns specs for items, triggers, effects, systems, or recipes directly. Supports batch mode: pass 'terms' array (max 20) to look up multiple items in one call instead of making separate requests. It is categorised as a Read tool in the Portals MCP Server, which means it retrieves data without modifying state.
lookup accepts 4 parameters: term, type, terms, category. 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 lookup: 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.
lookup 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 lookup 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 lookup. 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.
lookup 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 →