AI agents call get_request_base to retrieve information from Req without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a straightforward read operation that retrieves existing configuration data (the base URL). It has no write, execution, or destructive capability. The blast radius is minimal—an AI agent learning the current base URL poses no direct risk. Severity is low because the information returned is typically non-sensitive configuration.
From the tool's definition Tool name and description indicate it 'Returns the current base URL' — a pure query operation with no side effects. It retrieves configuration state without modifying or executing anything.
Attacks that exploit this kind of access
Returns the current base URL used for Request API calls. It is categorised as a Read tool in the Req MCP Server, which means it retrieves data without modifying state.
Register the Req MCP server in PolicyLayer and add a rule for get_request_base: 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 Req. Nothing to install.
get_request_base 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 get_request_base 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 get_request_base. 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.
get_request_base is provided by the Req MCP server (tarminarx/request-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the 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 →