pair_by_code
Pairs a physical screen with the 6-character code shown on https://display.agentview.de — the recommended first-time setup: ask the user to open that URL on the TV and read the code, then call this (creates and pairs in one step). Pass target_display_id to rebind an EXISTING display profile onto ...
This record as markdown: /tools/de-agentview-agentview-mcp/pair-by-code.md
What pair_by_code does on agentView
AI agents call pair_by_code to retrieve information from agentView without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
code | string | Yes | The 6-character pairing code shown on the display (e.g. 'AB3K7F'). |
access_token | string | — | Optional bearer token; prefer session_request_id. |
profile_name | string | — | Friendly name for the display (required for new pairing, ignored for rebind). Example: 'Lobby Screen'. |
target_display_id | string | — | To rebind: the existing display profile ID to switch to the new hardware. Omit for new display pairing. |
Parameters from the server's own tool schema.
Why pair_by_code is rated Low
Even though pair_by_code only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Risk signalsAccepts freeform code/query input (code) · Handles credentials or secrets (access_token) · Admin/system-level operation
Attacks that exploit this kind of access
The rule that runs pair_by_code safely
PolicyLayer is an MCP gateway: it sits between your AI agents and agentView, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For pair_by_code, this is the rule to start with:
pair_by_code is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect agentView, apply this rule, and every pair_by_code call is checked against it from then on.
Questions about pair_by_code
Pairs a physical screen with the 6-character code shown on https://display.agentview.de — the recommended first-time setup: ask the user to open that URL on the TV and read the code, then call this (creates and pairs in one step). Pass target_display_id to rebind an EXISTING display profile onto new hardware instead (keeps name, settings, content). Requires admin scope. It is categorised as a Read tool in the agentView MCP Server, which means it retrieves data without modifying state.
pair_by_code accepts 4 parameters: code, access_token, profile_name, target_display_id. Required: code. The full parameter table on this page comes from the server's own tool schema.
Register the agentView MCP server in PolicyLayer and add a rule for pair_by_code: 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 agentView. Nothing to install.
pair_by_code 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 pair_by_code 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 pair_by_code. 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.
pair_by_code is provided by the agentView MCP server (https://agentview.de/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on agentView, and thousands of servers like it.
This server
Across the catalogue