Get all users from the data table with their current filters and sorting applied
AI agents call get_users_table_data to retrieve information from React Tools without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a Read operation—it retrieves user data from a table without creating, modifying, or deleting any data. Severity is high rather than low because it retrieves potentially sensitive user information (personal data about multiple users), which could be misused by a rogue agent to exfiltrate PII or business-critical user records. However, it causes no direct harm or side effects on its own.
From the tool's definition Tool name is 'get_users_table_data' and description states 'Get all users from the data table with their current filters and sorting applied'. This is a data retrieval operation with no modification capabilities.
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access get_users_table_data gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and React Tools, and nothing reaches the server without passing your rules. This is the rule we recommend for get_users_table_data:
{
"version": "1",
"default": "deny",
"tools": {
"get_users_table_data": {}
}
} get_users_table_data 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 all users from the data table with their current filters and sorting applied. It is categorised as a Read tool in the React Tools MCP Server, which means it retrieves data without modifying state.
Register the React Tools MCP server in PolicyLayer and add a rule for get_users_table_data: 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 React Tools. Nothing to install.
get_users_table_data 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_users_table_data 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_users_table_data. 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_users_table_data is provided by the React Tools MCP server (mcp-fe/mcp-fe). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from React Tools, 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.
20 React Tools tools catalogued and risk-classified — across an index of 43,000+ MCP servers.