get_cursor_position

Get current mouse cursor position.

SERVERAos SOURCE@hybridlabor-api/aos

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/hybridlabor-api-aos/get-cursor-position.md

WHAT IT DOES

What get_cursor_position does on Aos

AI agents call get_cursor_position to retrieve information from Aos without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why get_cursor_position is rated Low

Retrieves cursor coordinates without side effects; read-only observation of system state.

From the tool's definition Get current mouse cursor position

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_cursor_position safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Aos, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_cursor_position, this is the rule to start with:

get_cursor_position Allowed

get_cursor_position is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_cursor_position": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Aos, apply this rule, and every get_cursor_position call is checked against it from then on.

FAQ

Questions about get_cursor_position

What does the get_cursor_position tool do? +

Get current mouse cursor position. It is categorised as a Read tool in the Aos MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_cursor_position? +

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

What risk level is get_cursor_position? +

get_cursor_position is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_cursor_position? +

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

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

get_cursor_position is provided by the Aos MCP server (@hybridlabor-api/aos). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Aos, and thousands of servers like it.

This server

All 719 Aos tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_file_snippet on ACE-MCP →get_torrent_detail on M-Team MCP Server →get_customer_data on 08-AI-Business-Agent → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →