This record as markdown: /tools/4da-mcp-server/get-context.md
What get_context does on 4da
AI agents call get_context to retrieve information from 4da without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_context is rated Low
This tool retrieves user context/information with no side effects or data modification. It fits the Read category as a simple query operation. Severity is low since it only accesses user context data without ability to modify, delete, or execute operations. Confidence is 0.85 rather than higher because the description is extremely sparse and doesn't fully clarify the scope of what user information is exposed.
From the tool's definition Tool name 'get_context' with description 'Get the user' indicates retrieval of user information without modification. The verb 'Get' and context of reading user data aligns with data retrieval operations.
Attacks that exploit this kind of access
The rule that runs get_context safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 4da, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_context, this is the rule to start with:
get_context 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 4da, apply this rule, and every get_context call is checked against it from then on.
Questions about get_context
Get the user. It is categorised as a Read tool in the 4da MCP Server, which means it retrieves data without modifying state.
Register the 4da MCP server in PolicyLayer and add a rule for get_context: 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 4da. Nothing to install.
get_context 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 get_context 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 get_context. 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.
get_context is provided by the 4da MCP server (4DA-Systems/4da-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 4da, and thousands of servers like it.
This server
Across the catalogue