This record as markdown: /tools/io-github-aibtcdev-mcp-server/jingswap-get-user-activity.md
What jingswap_get_user_activity does on Aibtc
AI agents call jingswap_get_user_activity 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.
Why jingswap_get_user_activity is rated Low
This tool retrieves user activity information without modifying, deleting, or executing external operations. The 'get' verb and read-only nature classify it as Read. Severity is low because retrieving user data poses minimal risk; an AI agent misusing this would only access information, not cause direct harm.
From the tool's definition Tool name contains 'get_user_activity' and description states 'Get a user', indicating a retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs jingswap_get_user_activity 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 jingswap_get_user_activity, this is the rule to start with:
jingswap_get_user_activity is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Aibtc, apply this rule, and every jingswap_get_user_activity call is checked against it from then on.
Questions about jingswap_get_user_activity
Get a user. It is categorised as a Read tool in the Aibtc MCP Server, which means it retrieves data without modifying state.
Register the Aibtc MCP server in PolicyLayer and add a rule for jingswap_get_user_activity: 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.
jingswap_get_user_activity 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 jingswap_get_user_activity 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 jingswap_get_user_activity. 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.
jingswap_get_user_activity 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.
More on Aibtc, and thousands of servers like it.
This server
Across the catalogue