Low Risk

get_study_status

get_study_status

How to control get_study_status ↓

What get_study_status does on Mcp Usercall

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

Low Risk

Why get_study_status needs a policy

The tool appears to retrieve status information about studies without modifying, deleting, or executing operations. The 'get_' prefix is conventionally used for read operations. Although the description is empty (lowering confidence slightly), the naming pattern and context from sibling tools strongly suggest this is a simple data retrieval operation with minimal blast radius if misused by an AI agent.

From the tool's definition Tool name 'get_study_status' indicates a retrieval operation that queries the status of an existing study.

Documented attack patterns abuse exactly the kind of access get_study_status gives an agent:

How to control get_study_status

PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Usercall, and nothing reaches the server without passing your rules. This is the rule we recommend for get_study_status:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_study_status": {}
  }
}

get_study_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Mcp Usercall — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_study_status

What does the get_study_status tool do? +

get_study_status. It is categorised as a Read tool in the Mcp Usercall MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_study_status? +

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

What risk level is get_study_status? +

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

Can I rate-limit get_study_status? +

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

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

get_study_status is provided by the Mcp Usercall MCP server (junetic/usercall-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mcp Usercall tool call.

Start from Mcp Usercall, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

5 Mcp Usercall tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.