position_search

Search for positions by name. Returns top 10 matching active positions sorted by creation date.

Server Evaluar MCP Server yarmijosp94/evaluar-mcp
Category Read
Risk class Low
Parameters 00 required

What position_search does on Evaluar MCP Server

AI agents call position_search to retrieve information from Evaluar MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why position_search needs a policy

This tool retrieves and searches existing position data from the Evaluar platform without modifying, creating, deleting, or executing any operations. It is a straightforward read-only query. The severity is low because misuse (e.g., searching for positions) poses minimal risk—at worst, an AI agent could gather information about available positions, which has no destructive or financial consequences.

From the tool's definition The tool 'position_search' performs a search operation that "returns top 10 matching active positions sorted by creation date." This is a query/retrieval operation with no data modification, deletion, or execution of external commands.

Questions about position_search

What does the position_search tool do? +

Search for positions by name. Returns top 10 matching active positions sorted by creation date. It is categorised as a Read tool in the Evaluar MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on position_search? +

Register the Evaluar MCP Server MCP server in PolicyLayer and add a rule for position_search: 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 Evaluar MCP Server. Nothing to install.

What risk level is position_search? +

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

Can I rate-limit position_search? +

Yes. Add a rate_limit block to the position_search 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 position_search completely? +

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

position_search is provided by the Evaluar MCP Server MCP server (yarmijosp94/evaluar-mcp). 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.