telescope_goto_object · Ascom MCP: Risk & Policy

WHAT IT DOES

What telescope_goto_object does on Ascom

AI agents invoke telescope_goto_object to trigger actions in Ascom. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why telescope_goto_object needs a policy

This tool triggers a physical operation on external hardware (slewing a telescope), which is an external action with real-world effects. It is not merely reading data, nor is it destructive or financial. It fits Execute because it drives a physical device based on arguments (the target celestial object), and misuse could cause mechanical damage or collisions depending on telescope environment.

From the tool's definition Slew telescope to a named celestial object

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

telescope_goto_object Rate-limited

telescope_goto_object stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "telescope_goto_object": {
      "limits": [
        {
          "counter": "telescope_goto_object_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Ascom, so you can run agents against it safely.

FAQ

Questions about telescope_goto_object

What does the telescope_goto_object tool do? +

Slew telescope to a named celestial object. It is categorised as a Execute tool in the Ascom MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on telescope_goto_object? +

Register the Ascom MCP server in PolicyLayer and add a rule for telescope_goto_object: 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_goto_object? +

telescope_goto_object is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit telescope_goto_object? +

Yes. Add a rate_limit block to the telescope_goto_object 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_goto_object completely? +

Set action: deny in the PolicyLayer policy for telescope_goto_object. 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_goto_object? +

telescope_goto_object 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.