Get User Secret Keys Retrieve all available secret keys for the authenticated user. These keys can be referenced in Python code execution for MCP tool integrations, but the actual values are never exposed for security. Perfect for: - Discovering what secret keys are available for workflow integra...
Part of the DataGen server.
Free to start. No card required.
AI agents call getUserSecrets to retrieve information from DataGen without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though getUserSecrets only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"getUserSecrets": {}
}
}See the full DataGen policy for all 20 tools.
These attack patterns abuse exactly the kind of access getUserSecrets gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Get User Secret Keys Retrieve all available secret keys for the authenticated user. These keys can be referenced in Python code execution for MCP tool integrations, but the actual values are never exposed for security. Perfect for: - Discovering what secret keys are available for workflow integrations - Understanding which MCP providers are configured - Planning workflows that require authentication with external services Returns: - List of available secret keys with their names and providers - Metadata including total count and available providers - Usage instructions for referencing secrets in executeCode Security Note: Only secret key names and metadata are returned, never the actual secret values.. It is categorised as a Read tool in the DataGen MCP Server, which means it retrieves data without modifying state.
Register the DataGen MCP server in PolicyLayer and add a rule for getUserSecrets: 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 DataGen. Nothing to install.
getUserSecrets 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 getUserSecrets 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 getUserSecrets. 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.
getUserSecrets is provided by the DataGen MCP server (kuoyusheng/datagendev). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 20 DataGen tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.