get_credit_card_pattern
Get regex pattern for credit card validation.
This record as markdown: /tools/io-tinyfn-tinyfn/get-credit-card-pattern.md
What get_credit_card_pattern does on TinyFn
AI agents call get_credit_card_pattern to retrieve information from TinyFn without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
card_type | string | — | Type: visa, mastercard, amex, discover, any |
Parameters from the server's own tool schema.
Why get_credit_card_pattern is rated Low
This tool purely retrieves and returns a regex pattern for validation purposes. It does not execute validation, create, modify, delete, or process any actual data. The pattern itself is static reference material used for client-side validation logic. No data is written, no external operations are triggered, and no financial transactions occur.
From the tool's definition Tool name is 'get_credit_card_pattern' and description states it returns a 'regex pattern for credit card validation.' This retrieves a pattern string with no side effects.
Attacks that exploit this kind of access
The rule that runs get_credit_card_pattern safely
PolicyLayer is an MCP gateway: it sits between your AI agents and TinyFn, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_credit_card_pattern, this is the rule to start with:
get_credit_card_pattern 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 TinyFn, apply this rule, and every get_credit_card_pattern call is checked against it from then on.
Questions about get_credit_card_pattern
Get regex pattern for credit card validation. It is categorised as a Read tool in the TinyFn MCP Server, which means it retrieves data without modifying state.
get_credit_card_pattern accepts 1 parameter: card_type. The full parameter table on this page comes from the server's own tool schema.
Register the TinyFn MCP server in PolicyLayer and add a rule for get_credit_card_pattern: 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 TinyFn. Nothing to install.
get_credit_card_pattern 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_credit_card_pattern 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_credit_card_pattern. 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_credit_card_pattern is provided by the TinyFn MCP server (https://api.tinyfn.io/mcp/all/). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on TinyFn, and thousands of servers like it.
This server
Across the catalogue