This record as markdown: /tools/io-github-devopam-mcpg/retrieve-with-context.md
What retrieve_with_context does on Mcpg
AI agents call retrieve_with_context 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 retrieve_with_context is rated Low
Although the description is empty (lowering confidence from 0.9 to 0.7), the name strongly suggests a retrieval operation that queries data without side effects. On a PostgreSQL MCP server, 'retrieve' typically means SELECT queries.
From the tool's definition The tool name 'retrieve_with_context' indicates data retrieval functionality, consistent with the Read category pattern of 'get, fetch' operations on a PostgreSQL server.
Attacks that exploit this kind of access
The rule that runs retrieve_with_context 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 retrieve_with_context, this is the rule to start with:
retrieve_with_context 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 retrieve_with_context call is checked against it from then on.
Questions about retrieve_with_context
retrieve_with_context 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 retrieve_with_context: 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.
retrieve_with_context 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 retrieve_with_context 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 retrieve_with_context. 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.
retrieve_with_context 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