Classify a Portals gameplay request against the shared harness grounding layer. Returns supported_directly, supported_via_workaround, unsupported, or unknown with matched capabilities, limitations, patterns, sources, and next actions. Use this before making platform capability claims or proposing...
AI agents call resolve_gameplay_capability 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 | Gameplay feature or platform capability to classify, for example: locked door, coin counter, native SQL database. |
max_results | integer | — | Maximum matched capabilities, limitations, and patterns to return (default: 5). |
Parameters from the server's own tool schema.
This tool performs a classification/lookup operation against a knowledge base (grounding layer) and returns structured information about platform capabilities. It reads and returns data without creating, modifying, executing, or deleting anything. It is purely a query/advisory tool used before making capability claims.
From the tool's definition Classify a Portals gameplay request against the shared harness grounding layer. Returns supported_directly, supported_via_workaround, unsupported, or unknown with matched capabilities, limitations, patterns, sources, and next actions.
Risk signalsAccepts freeform code/query input (query)
Attacks that exploit this kind of access
Classify a Portals gameplay request against the shared harness grounding layer. Returns supported_directly, supported_via_workaround, unsupported, or unknown with matched capabilities, limitations, patterns, sources, and next actions. Use this before making platform capability claims or proposing game logic. It is categorised as a Read tool in the Portals MCP Server, which means it retrieves data without modifying state.
resolve_gameplay_capability accepts 2 parameters: query, max_results. 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 resolve_gameplay_capability: 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.
resolve_gameplay_capability 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 resolve_gameplay_capability 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 resolve_gameplay_capability. 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.
resolve_gameplay_capability 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 →