get_section

Get a specific PayHere documentation section by topic name. Supports fuzzy matching.

Server PayHere Documentation MCP Server theepankaja/payhere-agent-docs
Category Read
Risk class Low
Parameters 00 required

What get_section does on PayHere Documentation MCP Server

AI agents call get_section 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.

Why get_section needs a policy

This tool retrieves and queries documentation content from the PayHere API reference materials. It has no side effects, does not execute code, does not modify or delete data, and does not involve financial transactions. It is a straightforward documentation lookup utility, fitting the 'Read' category for information retrieval operations.

From the tool's definition Tool description states 'Get a specific PayHere documentation section' with fuzzy matching support. The verb 'get' combined with the purpose of retrieving documentation content indicates pure data retrieval with no modification, deletion, or execution…

Questions about get_section

What does the get_section tool do? +

Get a specific PayHere documentation section by topic name. Supports fuzzy matching. It is categorised as a Read tool in the PayHere Documentation MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_section? +

Register the PayHere Documentation MCP Server MCP server in PolicyLayer and add a rule for get_section: 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.

What risk level is get_section? +

get_section is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_section? +

Yes. Add a rate_limit block to the get_section 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.

How do I block get_section completely? +

Set action: deny in the PolicyLayer policy for get_section. 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.

What MCP server provides get_section? +

get_section 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.