AI agents call fetch_profile to retrieve information from Test without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves profile information without side effects. It performs a read-only query operation. Severity is low because profile data access, while potentially sensitive in scope, does not enable unauthorized actions on other systems or financial operations. The sibling tools (fetch_leaderboard, fetch_token_broadcasts, fetch_token_data) confirm this server's read-focused nature.
From the tool's definition Tool name is 'fetch_profile' and description states 'Fetch detailed profile data' — the verb 'fetch' indicates retrieval without modification. The context (Vector trader profile data) suggests querying existing data.
Attacks that exploit this kind of access
Fetch detailed profile data for a Vector trader. It is categorised as a Read tool in the Test MCP Server, which means it retrieves data without modifying state.
Register the Test MCP server in PolicyLayer and add a rule for fetch_profile: 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 Test. Nothing to install.
fetch_profile 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 fetch_profile 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 fetch_profile. 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.
fetch_profile is provided by the Test MCP server (jusscubs/mcp-server-test). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
fetch_profile is one line of Test's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →