This record as markdown: /tools/io-github-devopam-mcpg/fetch-cursor.md
What fetch_cursor does on Mcpg
AI agents call fetch_cursor to retrieve information from Mcpg without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why fetch_cursor is rated Low
The name 'fetch_cursor' indicates fetching/retrieving data from a cursor, which is a standard database READ operation. Cursors are used to iterate over query results without side effects. However, confidence is moderate (0.7) because the description is empty, preventing verification of exact behavior.
From the tool's definition Tool name 'fetch_cursor' suggests data retrieval via database cursor mechanism, typical of READ operations in PostgreSQL contexts. No destructive, financial, or execute-class keywords present.
Attacks that exploit this kind of access
The rule that runs fetch_cursor safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcpg, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For fetch_cursor, this is the rule to start with:
fetch_cursor is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcpg, apply this rule, and every fetch_cursor call is checked against it from then on.
Questions about fetch_cursor
fetch_cursor is a read tool on the Mcpg MCP server. It is categorised as a Read tool in the Mcpg MCP Server, which means it retrieves data without modifying state.
Register the Mcpg MCP server in PolicyLayer and add a rule for fetch_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 Mcpg. Nothing to install.
fetch_cursor is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the fetch_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.
Set action: deny in the PolicyLayer policy for fetch_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.
fetch_cursor is provided by the Mcpg MCP server (pypi:mcpg). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcpg, and thousands of servers like it.
This server
Across the catalogue