get_current_user_info

THE RISK

Low Risk

Why get_current_user_info needs a policy

This tool retrieves user information from the platform API without creating, modifying, deleting, or executing operations. It is a straightforward read operation similar to 'get' or 'fetch' patterns. The blast radius of misuse is minimal—an AI agent would only gain visibility into user profile data, which is typically low-sensitivity metadata already accessible to authenticated users.

From the tool's definition Tool name 'get_current_user_info' and description 'Get current user information directly from platform API' indicate data retrieval with no modification or side effects.

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

POLICY

How to control get_current_user_info

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

policy.json

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

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

Create a free account and register Git MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Git MCP Server tools

Destructive delete_project Delete a project from the specified platform Destructive close_merge_request close_merge_request Write close_issue Close an issue Write close_milestone Close a milestone Write create_fork create_fork Write create_issue Create a new issue in a project Write create_issue_comment Create a comment on an issue Write create_merge_request create_merge_request

All 33 Git MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_current_user_info

What does the get_current_user_info tool do? +

Get current user information directly from platform API. It is categorised as a Read tool in the Git MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_current_user_info? +

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

What risk level is get_current_user_info? +

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

Can I rate-limit get_current_user_info? +

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

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

get_current_user_info is provided by the Git MCP Server MCP server (yumeminami/git_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Git MCP Server tool call.

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

CHECK YOUR STACK →