zest_get_position

Get user

SERVERAibtc SOURCEaibtcdev/aibtc-mcp-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity verified Pull the record →

This record as markdown: /tools/io-github-aibtcdev-mcp-server/zest-get-position.md

WHAT IT DOES

What zest_get_position does on Aibtc

AI agents call zest_get_position to retrieve information from Aibtc without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why zest_get_position is rated Low

This tool retrieves or queries position information for a user, consistent with Read category behavior. The incomplete description ('Get user') provides minimal detail, reducing confidence slightly, but the core function is clearly a data retrieval operation with no destructive, financial, or execution implications.

From the tool's definition Tool name 'zest_get_position' and description 'Get user' indicate retrieval of user position data without modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs zest_get_position safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Aibtc, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For zest_get_position, this is the rule to start with:

zest_get_position Allowed

zest_get_position is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "zest_get_position": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Aibtc, apply this rule, and every zest_get_position call is checked against it from then on.

FAQ

Questions about zest_get_position

What does the zest_get_position tool do? +

Get user. It is categorised as a Read tool in the Aibtc MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on zest_get_position? +

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

What risk level is zest_get_position? +

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

Can I rate-limit zest_get_position? +

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

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

zest_get_position is provided by the Aibtc MCP server (aibtcdev/aibtc-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Aibtc, and thousands of servers like it.

This server

All 358 Aibtc tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →