> For the complete documentation index, see [llms.txt](https://docs.stacks.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stacks.co/cookbook/clarity/cryptography-and-security/helper-function-to-restrict-contract-calls.md).

# Helper function to restrict contract calls

{% code fullWidth="false" expandable="true" %}

```clarity
;; Check if caller is a standard principal (user wallet)
(define-private (is-standard-principal-call)
  (is-none (get name (unwrap! (principal-destruct? contract-caller) false)))
)

;; Public function restricted to direct user calls
(define-public (user-only-function (amount uint))
  (begin
    (asserts! (is-standard-principal-call) (err u401))
    ;; Function logic here
    (ok true)
  )
)
```

{% endcode %}

### Description

Implement access control to ensure functions can only be called by users, not other contracts

### Use Cases

* Preventing contract-to-contract reentrancy attacks
* Ensuring human-initiated transactions for governance
* Restricting token minting to direct user actions
* Protecting admin functions from automated calls

### Key Concepts

* **Standard principals** - User wallets (SP/ST addresses)
* **Contract principals** - Deployed contracts (address.contract-name)
* **contract-caller** - The immediate caller of the current function
* **tx-sender** - The original transaction initiator


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.stacks.co/cookbook/clarity/cryptography-and-security/helper-function-to-restrict-contract-calls.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.