Get detailed information about a specific influencer.
AI agents call social_get_influencer to retrieve information from BNB Chain MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves publicly available or stored influencer profile information without side effects. It is a simple data query operation that does not create, modify, delete, or execute any actions. The blast radius of misuse is minimal - at worst, an agent could retrieve information about various influencers, which poses no financial, destructive, or operational risk.
From the tool's definition Tool name is 'social_get_influencer' and description states 'Get detailed information about a specific influencer' - purely a retrieval operation with no modification, deletion, or execution of code/commands.
Documented attack patterns abuse exactly the kind of access social_get_influencer gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and BNB Chain MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for social_get_influencer:
{
"version": "1",
"default": "deny",
"tools": {
"social_get_influencer": {}
}
} social_get_influencer is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get detailed information about a specific influencer. It is categorised as a Read tool in the BNB Chain MCP MCP Server, which means it retrieves data without modifying state.
Register the BNB Chain MCP server in PolicyLayer and add a rule for social_get_influencer: 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 BNB Chain MCP. Nothing to install.
social_get_influencer 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 social_get_influencer 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 social_get_influencer. 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.
social_get_influencer is provided by the BNB Chain MCP server (nirholas/bnbchain-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 1240 BNB Chain MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
1240 BNB Chain MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.