telescope_connect

Connect to an ASCOM telescope.

Server Ascom stellarpunk/mcp-server-ascom
Category Write
Risk class Medium
Parameters 00 required

What telescope_connect does on Ascom

AI agents use telescope_connect to create or update resources in Ascom — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ascom environment.

Why telescope_connect needs a policy

Connecting to a telescope establishes a connection/session with the device, which is a reversible state change (can be disconnected). It modifies the connection state but does not read data, execute commands, or cause destructive/financial effects. Severity is low as misuse at most results in an unintended telescope connection.

From the tool's definition Connect to an ASCOM telescope

Questions about telescope_connect

What does the telescope_connect tool do? +

Connect to an ASCOM telescope. It is categorised as a Write tool in the Ascom MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on telescope_connect? +

Register the Ascom MCP server in PolicyLayer and add a rule for telescope_connect: 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 Ascom. Nothing to install.

What risk level is telescope_connect? +

telescope_connect is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit telescope_connect? +

Yes. Add a rate_limit block to the telescope_connect 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.

How do I block telescope_connect completely? +

Set action: deny in the PolicyLayer policy for telescope_connect. 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.

What MCP server provides telescope_connect? +

telescope_connect is provided by the Ascom MCP server (stellarpunk/mcp-server-ascom). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.