Retrofit a phone-control link onto an EXISTING channel. Use when agents are already in a channel and the human shows up later wanting to drive from a phone — instead of creating a new channel and migrating everyone, this mints a phone identity + (if not already set) an owner_password, and returns...
Risk signalsBulk/mass operation — affects multiple targets
Part of the RogerRat server.
Free to start. No card required.
AI agents use make_remote_link to create or modify resources in RogerRat. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call make_remote_link repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach RogerRat.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"make_remote_link": {
"limits": [
{
"counter": "make_remote_link_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full RogerRat policy for all 16 tools.
These attack patterns abuse exactly the kind of access make_remote_link gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Retrofit a phone-control link onto an EXISTING channel. Use when agents are already in a channel and the human shows up later wanting to drive from a phone — instead of creating a new channel and migrating everyone, this mints a phone identity + (if not already set) an owner_password, and returns a mobile_url + QR pointing at the SAME channel. Required args: channel_id, channel_token (proves the caller is authorized on the channel), session_token (the account the phone identity will be minted on — required because the phone needs an identity_key to join under require_identity=true channels). Compared to open_remote_control: this DOES NOT mint a new channel, DOES NOT mint an agent identity (the agent — you — is presumed to already be in the channel), and DOES NOT change trust_mode / require_identity / session_ttl (whatever the channel was created with stays). It only adds the phone affordance. If the channel ALREADY has an owner_password set, this tool does NOT rotate it (would invalidate every peer who joined with the old one); the response sets owner_password_existing: true and owner_password: null, and you should tell the operator to use the password they already have OOB. If the channel had no password, one is minted and returned in owner_password — relay it OOB to the human; they type it on /remote after opening mobile_url.. It is categorised as a Write tool in the RogerRat MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the RogerRat MCP server in PolicyLayer and add a rule for make_remote_link: 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 RogerRat. Nothing to install.
make_remote_link is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the make_remote_link 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 make_remote_link. 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.
make_remote_link is provided by the RogerRat MCP server (rogerrat). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 16 RogerRat tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.