Get authentication configuration for an API
AI agents call get_auth_info to retrieve information from OpenAPI Search MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries authentication configuration data from an OpenAPI specification. It performs a read-only lookup operation with no side effects—it neither modifies data, executes code, deletes resources, nor commits financial transactions. The action is informational only, fitting the 'Read' category for data retrieval tools.
From the tool's definition Tool name 'get_auth_info' and description 'Get authentication configuration for an API' indicate retrieval of existing authentication metadata without modification or execution of operations.
Attacks that exploit this kind of access
Get authentication configuration for an API. It is categorised as a Read tool in the OpenAPI Search MCP Server MCP Server, which means it retrieves data without modifying state.
Register the OpenAPI Search MCP Server MCP server in PolicyLayer and add a rule for get_auth_info: 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 OpenAPI Search MCP Server. Nothing to install.
get_auth_info 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_auth_info 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_auth_info. 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_auth_info is provided by the OpenAPI Search MCP Server MCP server (sheepion/openapi-search-mcp). 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 →