Get documentation for a specific PayHere API. Understands aliases like
AI agents call get_api_reference to retrieve information from PayHere Documentation MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves API documentation—a read operation with no side effects. It returns information to help users understand the PayHere API but does not execute transactions, modify data, or trigger external operations. The sibling tools (get_sdk_guide, get_section, list_topics, search_docs) further confirm this server is purely informational.
From the tool's definition Tool name 'get_api_reference' and description indicate it retrieves documentation for a specific PayHere API.
Attacks that exploit this kind of access
Get documentation for a specific PayHere API. Understands aliases like. It is categorised as a Read tool in the PayHere Documentation MCP Server MCP Server, which means it retrieves data without modifying state.
Register the PayHere Documentation MCP Server MCP server in PolicyLayer and add a rule for get_api_reference: 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 PayHere Documentation MCP Server. Nothing to install.
get_api_reference 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_api_reference 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_api_reference. 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_api_reference is provided by the PayHere Documentation MCP Server MCP server (theepankaja/payhere-agent-docs). 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 →