Connect Cloudflare Agents SDK Documentation to Raycast
Give Raycast governed access to Cloudflare Agents SDK Documentation through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Cloudflare Agents SDK Documentation to Raycast in four steps
Admins approve the server once. Everyone in Raycast then gets it through the same governed connection.
- 1
Approve Cloudflare Agents SDK Documentation in Runlayer
Add Cloudflare Agents SDK Documentation from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect Raycast to Runlayer
Users add the Runlayer Plugin to Raycast by following Runlayer’s setup guide. Raycast reaches Cloudflare Agents SDK Documentation’s tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Raycast setup guide - 3
Sign in to Cloudflare Agents SDK Documentation
Sign in the way Cloudflare Agents SDK Documentation requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Cloudflare Agents SDK Documentation from Raycast
Cloudflare Agents SDK Documentation’s approved tools appear in Raycast. Every call is checked against policy and recorded.
Tools
Cloudflare Agents SDK Documentation tools in Raycast
Cloudflare Agents SDK Documentation reports its tools when your organization connects it, so the list depends on your deployment.
Control
What Runlayer can see and stop in Raycast
Some controls apply to every client at the gateway. Others depend on what Raycast exposes to Runlayer.
Gateway policy (available)
Every Cloudflare Agents SDK Documentation call from Raycast passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Raycast as the client, the tool, and the policy and scanner decisions.
Native enforcement adapter (not available)
Runlayer has no device-side adapter for Raycast yet, so control happens at the gateway.
Frequently asked questions
Connect more