get_screen_cursor

Returns the current cursor position and the text of the line the cursor is on. Lightweight alternative to reading the full screen.

Server Interactive Shell MCP lightos/interactive-shell-mcp
Category Read
Risk class Low
Parameters 00 required

What get_screen_cursor does on Interactive Shell MCP

AI agents call get_screen_cursor to retrieve information from Interactive Shell MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_screen_cursor needs a policy

This tool retrieves information about the current state of a shell session (cursor position and current line text). It performs no writes, deletions, or command execution. The information returned could be sensitive if the shell contains credentials or private data, but the tool itself is purely read-only.

From the tool's definition Tool description states it 'Returns the current cursor position and the text of the line the cursor is on' - a retrieval operation with no side effects.

Questions about get_screen_cursor

What does the get_screen_cursor tool do? +

Returns the current cursor position and the text of the line the cursor is on. Lightweight alternative to reading the full screen. It is categorised as a Read tool in the Interactive Shell MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_screen_cursor? +

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

What risk level is get_screen_cursor? +

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

Can I rate-limit get_screen_cursor? +

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

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

get_screen_cursor is provided by the Interactive Shell MCP server (lightos/interactive-shell-mcp). 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.